From: Con Kolivas <kernel@kolivas.org>
To: "Martin MOKREJŠ" <mmokrejs@ribosome.natur.cuni.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: openafs is really faster on linux-2.4. than 2.6
Date: Thu, 18 Aug 2005 23:31:55 +1000 [thread overview]
Message-ID: <200508182331.56217.kernel@kolivas.org> (raw)
In-Reply-To: <43048D81.80402@ribosome.natur.cuni.cz>
On Thu, 18 Aug 2005 23:30, Martin MOKREJŠ wrote:
> But that is very short and does not affect the interpretation here.
Crap. The sync can take ages.
> The throughput is clearly lower on 2.6 kernel and definitely the
> CPU is in my eyes unnecessarily blocked... Why is the CPU in the
> wait state instead of idle (this is teh problem on 2.6 series
> but CPU is free on 2.4 series)? That's the main problem I think at the
> moment.
There is no wait state accounted for in 2.4 so you won't see it.
Con
> Con Kolivas wrote:
> > On Thu, 18 Aug 2005 22:48, Martin MOKREJŠ wrote:
> >>I think the problem here is outside afs.
> >>Just doing this dd test but writing data directly to the ext2
> >>target gives same behaviour, i.e. on 2.4 kernel I see most of the
> >>CPU idle but on 2.6 kernel all that CPU amount is shown as in
> >>wait state. And the numbers from 2.4 kernel show higher throughput
> >>compared to the 2.6 kernel (regardless the the PREEMPT or no PREEMPT
> >>was used).
> >
> > Don't forget to include sync time.
next prev parent reply other threads:[~2005-08-18 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43032109.6030709@ribosome.natur.cuni.cz>
[not found] ` <4303293D.10805@ribosome.natur.cuni.cz>
[not found] ` <430339AF.7080102@ribosome.natur.cuni.cz>
[not found] ` <4303B70B.9080707@ribosome.natur.cuni.cz>
2005-08-18 10:52 ` openafs is really faster on linux-2.4. than 2.6 Martin MOKREJŠ
2005-08-18 11:01 ` Christoph Hellwig
2005-08-18 12:48 ` Martin MOKREJŠ
2005-08-18 12:57 ` Con Kolivas
2005-08-18 13:30 ` Martin MOKREJŠ
2005-08-18 13:31 ` Con Kolivas [this message]
2005-08-18 16:04 ` Martin MOKREJŠ
2005-08-18 17:38 ` Lee Revell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508182331.56217.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@ribosome.natur.cuni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox