From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: "Andrea Arcangeli" <andrea@suse.de>
Cc: <linux-kernel@vger.kernel.org>, "Rik van Riel" <riel@conectiva.com.br>
Subject: Re: async buffer flushing reported slowdown (could be a driver issue?)
Date: Thu, 17 Jan 2002 19:28:59 -0500 [thread overview]
Message-ID: <012a01c19fb7$1f39d580$02c8a8c0@kroptech.com> (raw)
In-Reply-To: <20020116200459.E835@athlon.random> <056c01c19ed4$f0e77300$02c8a8c0@kroptech.com> <20020117151745.H4847@athlon.random>
Andrea Arcangeli wrote:
> On Wed, Jan 16, 2002 at 04:29:54PM -0500, Adam Kropelin wrote:
> > Andrea Arcangeli wrote:
> > <snip>
> > >I don't have a single bugreport about the current 2.4.18pre2aa2 VM (except
> > >perhaps the bdflush wakeup that seems to be a little too late and that
deals to
> > >lower numbers with slow write load etc.., fixable with bdflush tuning).
> >
> > As reported[0] in the above-mentioned thread, the bdflush tuning parameters
> > you suggested made no difference in my test case other than slightly
adjusting
> > the temporal relationship between writeout and file transfer. -aa still
performs
> > slightly worse than both 2.4.17 stock and -rmap. 2.4.13-ac7 currently beats
> > all competitors.
>
> Then can you verify the bandwith you get out of the network card is the
> same across 2.4.13-ac7 and all the other kernels you are trying. Also
I'll check that and get back to you.
> please check with an hdparm -t the speed you get out of IDE is the same.
There is no IDE in the system. The destination for the file transfer is on
cpqarray RAID5. Do you have a recommendation for how I test the transfer rate of
that without stressing the VM?
> This sounds like some driver changed (note that -ac is used to queue
> lots of driver updates) and that made the difference. Otherwise if we
> wakeup bdflush early enough I don't see why it takes more time.
One of my original tests[0] was to take the cpqarray update from -ac and bring
it forward to 2.4.17. I saw about 20 sec improvement with that, still not
competitive overall with -ac performance. I'll try doing the same with eepro
driver, which is the NIC I'm using.
--Adam
[0]
http://www.kroptech.com:8300/mailimport/showmsg.php?msg_id=49714&db_name=linux_k
ernel
next prev parent reply other threads:[~2002-01-18 0:29 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L.0201162235480.32617-100000@imladris.surriel .com>
2002-01-16 19:04 ` Rik spreading bullshit about VM Andrea Arcangeli
2002-01-16 20:11 ` Jose Luis Domingo Lopez
2002-01-16 20:58 ` Richard Gooch
2002-01-16 21:10 ` Dave Jones
2002-01-16 21:17 ` Rik van Riel
2002-01-17 13:42 ` [lkml] " Ian Soboroff
2002-01-18 3:21 ` ...Re: " Dan Mann
2002-01-17 0:20 ` Luigi Genoni
2002-01-16 21:17 ` Craig Knox
2002-01-16 20:58 ` Bongani Hlope
2002-01-16 20:55 ` John Levon
2002-01-16 21:21 ` Bongani Hlope
2002-01-16 21:29 ` Adam Kropelin
2002-01-17 14:17 ` async buffer flushing reported slowdown (could be a driver issue?) Andrea Arcangeli
2002-01-18 0:28 ` Adam Kropelin [this message]
2002-01-16 21:58 ` Rik spreading bullshit about VM Diego Calleja
2002-01-16 22:02 ` Rik van Riel
2002-01-17 14:35 ` bugfix backed out Andrea Arcangeli
2002-01-17 15:04 ` Rik van Riel
2002-01-17 15:52 ` Andrea Arcangeli
2002-01-17 14:25 ` oom failures with mem=4m Andrea Arcangeli
2002-01-16 21:59 ` Rik spreading bullshit about VM Diego Calleja
2002-01-16 22:44 ` Chris Chabot
2002-01-17 8:18 ` Christoph Rohland
2002-01-17 14:13 ` blkdev speedup Andrea Arcangeli
2002-01-17 0:07 ` Rik spreading bullshit about VM Erik Mouw
2002-01-17 0:25 ` J Sloan
2002-01-17 1:15 ` Erik Mouw
2002-01-17 17:40 ` bill davidsen
2002-01-17 14:14 ` Alan Cox
2002-01-18 4:30 ` Bosko Radivojevic
2002-01-18 4:36 ` vm philosophising Rik van Riel
2002-01-18 4:58 ` Matthew Johnson
2002-01-18 5:12 ` Rik van Riel
2002-01-18 5:18 ` Ryan Cumming
2002-01-18 5:43 ` Matthew Johnson
2002-01-21 17:55 ` Bill Davidsen
2002-01-18 6:05 ` Matthew Johnson
2002-01-18 14:42 ` Tommy Faasen
2002-01-18 15:52 ` listmail
2002-01-21 15:50 ` The Doctor What
2002-01-21 16:16 ` Mike Harrold
2002-01-18 15:55 ` Mr. Shannon Aldinger
2002-01-18 18:39 ` Oliver Xymoron
2002-01-18 19:23 ` Alan Cox
2002-01-18 20:17 ` David Schwartz
2002-01-18 21:39 ` Alan Cox
2002-01-19 4:42 ` David Luyer
2002-01-19 18:00 ` Rob Landley
2002-01-20 5:42 ` Stevie O
2002-01-17 0:38 ` Rik spreading bullshit about VM Rik van Riel
2002-01-17 1:50 ` Nicolas Pitre
2002-01-17 11:45 ` Rik van Riel
2002-01-17 12:02 ` Stephan von Krawczynski
2002-01-17 2:14 ` Andrea Scrimieri
2002-01-17 12:07 ` Rik van Riel
2002-01-17 13:11 ` Andrea Scrimieri
2002-01-17 13:15 ` Rik van Riel
2002-01-17 14:02 ` Alan Cox
2002-01-17 21:41 ` Trever L. Adams
2002-01-18 1:46 ` brian
2002-01-17 1:52 ` Stephen Satchell
2002-01-17 13:26 ` Alan Cox
2002-01-17 15:10 ` clarification about redhat and vm Andrea Arcangeli
2002-01-17 15:21 ` Rik van Riel
2002-01-17 16:17 ` Alan Cox
2002-01-17 16:31 ` Andrea Arcangeli
2002-01-18 16:46 ` Wilhelm Nuesser
2002-01-18 19:07 ` Andrea Arcangeli
2002-01-19 10:50 ` Christoph Rohland
2002-01-19 13:54 ` Alan Cox
2002-01-19 17:38 ` Andrea Arcangeli
2002-01-18 16:53 ` Willi Nüßer
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='012a01c19fb7$1f39d580$02c8a8c0@kroptech.com' \
--to=akropel1@rochester.rr.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.