From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: DMA transfers in 2.5.67
Date: Fri, 18 Apr 2003 07:25:46 -0400 [thread overview]
Message-ID: <200304180729_MC3-1-34EE-CBE8@compuserve.com> (raw)
Andrew Morton wrote:
> > Chuck Ebbert <76306.1226@compuserve.com> wrote:
> > >
> > > # mount /ext3_fs
> > > # time dd if=/ext3_fs/100MiB_file of=/dev/null bs=32k
> > >
> > > 2.4.20aa1 : 3.3 sec (exactly what I expect to see)
> > > 2.5.66 : 6.6 sec
> >
> > With this test 2.4 will leave a lot more unwritten dirty data in memory.
> >
> > You should include a `sync' in the timings.
>
> Well you should include the sync if you're writing to disk ;)
:)
All is not beer and skittles here with Andrea's kernel, though.
Sometimes instead of 31MB/sec I get this with 1 sequential stream:
1 0 0 0 1232 1120 47988 0 0 14928 0 3834 7534 1 44 55
1 0 0 0 1372 1120 47848 0 0 14704 0 3778 7446 0 32 68
1 0 0 0 1464 1064 47816 0 0 14880 0 3822 7501 1 43 56
1 0 0 0 1336 1064 47944 0 0 14844 0 3813 7493 0 29 71
1 0 0 0 1432 1064 47848 0 0 14748 32 3800 7467 0 41 59
1 0 0 0 1532 1064 47748 0 0 13976 0 3596 7045 1 33 66
Pretty high context switch and interrupt rates for a PPro 200, huh?
And I can't reliably reproduce it (so far...)
------
Chuck
next reply other threads:[~2003-04-18 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 11:25 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 9:45 Chuck Ebbert
2003-04-16 10:11 ` Andrew Morton
2003-04-16 10:13 ` Andrew Morton
2003-04-16 10:13 ` Måns Rullgård
2003-04-15 20:01 Måns Rullgård
2003-04-15 20:31 ` Alan Cox
2003-04-15 21:38 ` Måns Rullgård
2003-04-15 20:48 ` Alan Cox
2003-04-15 22:09 ` Måns Rullgård
2003-04-16 8:36 ` Ivan Kokshaysky
2003-04-16 8:43 ` Måns Rullgård
2003-04-16 8:59 ` Måns Rullgård
2003-04-16 9:30 ` Måns Rullgård
2003-04-16 10:01 ` Ivan Kokshaysky
2003-04-16 10:11 ` Måns Rullgård
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=200304180729_MC3-1-34EE-CBE8@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®