On Tue, 7 Feb 2006 21:24:11 -0500, Benjamin LaHaise <[email protected]> wrote:
>On Wed, Feb 08, 2006 at 01:11:49PM +1100, Grant Coady wrote:
>> This console sluggishness is noticeable enough on older hardware for me to
>> forgo exercising 2.6.latest.stable bugs for much time on it ;)
>>
>> For those suffering deja vu, yes, I reported this last month (or, recently).
>
>This bug report is a bit vague in terms of what the problem is -- the
>test case hits 3 major subsystems (io, vm, net), all of which have changed
>rather substantially in the course of 2.6 development.
Vague 'cos I do not know where the problem is. One might say slowdown
is like a near a 1ms delay per line output, but slowdown does not
correlate to kernel tick frequency. :(
> Would it be possible
>to profile the system using oprofile to get an idea what the hotspots are?
Perhaps, I've yet to try that.
>Have you compared basic hard disk throughput with hdparm, as well as
>ensuring DMA is enabled with 32 bit io? What about testing network
>performance with netperf (or a netcat of /dev/zero)? A few more data points
>would be quite helpful.
Yes, the gross datapoints such as basic net i/o, disk i/o, say 2.6 is
better/faster than 2.4 on this hardware, my problem is how to describe
measured console slowdown in terms meaningful to you.
I'll take a look at oprofile, report back if I can make sense of it ;)
Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]