Skip to contentSkip to conversation

2.4.10-ac10-preempt lmbench output.

DISCUSSION Robert Love 2 participants 3 messages Oct 10, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 3 lines · Dieter Nützel

Robert you are running a dual PIII system, right?
Could that be the ground why you aren't see the hiccup with your nice preempt patch? Are you running ReiserFS or EXT2/3?

No, I am on a single P3-733. I am using ext3.

I have had reports from users on both UP and SMP systems that say audio playback is undisturbed during heavy I/O with preempt-kernel patch. Of course, I don't know their definition of undisturbed...but I would wager it doesn't include 2-3s skips.

Robert Love

#2 lore raw
Quoted 6 lines · Robert Love
Quoted 3 lines · Dieter Nützel

Robert you are running a dual PIII system, right?
Could that be the ground why you aren't see the hiccup with your nice preempt patch? Are you running ReiserFS or EXT2/3?

No, I am on a single P3-733. I am using ext3.

Oh, I'm not using Linus's tree, either.

Right now I am 2.4.10-ac10 + preempt-kernel + Rik's eatcache

Robert Love

#3 lore raw
In reply to a message not in the archive
Quoted 11 lines · Robert Love
Quoted 3 lines · Dieter Nützel

Robert you are running a dual PIII system, right?
Could that be the ground why you aren't see the hiccup with your nice preempt patch? Are you running ReiserFS or EXT2/3?

No, I am on a single P3-733. I am using ext3.

I have had reports from users on both UP and SMP systems that say audio playback is undisturbed during heavy I/O with preempt-kernel patch. Of course, I don't know their definition of undisturbed...but I would wager it doesn't include 2-3s skips.

If it's purerly I/O even mainline that is missing the reschedule points shouldn't matter.

Infact the only thing that hurts during pure I/O (I mean not I/O from cache, I mean real I/O to disk) is the browse of the lru dirty lists in buffer.c and the vm lists (the latter are covered in latest 2.4). And just the preemptive patch cannot help there since they're both covered by locks and the explicit checks in the preemptive patch will get a result equal to the lowlatency approch.

If it's mixed I/O half from cache and half from disk, then the lack of reschedule points could be the culprit of course.

Andrea