public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fsync delays for a long time.
Date: Sun, 17 Feb 2002 08:45:31 -0800	[thread overview]
Message-ID: <20020217164531.GA19111@netnation.com> (raw)
In-Reply-To: <20020215172436.GA6842@netnation.com> <Pine.LNX.3.96.1020217074231.30060G-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020217074231.30060G-100000@gatekeeper.tmr.com>

On Sun, Feb 17, 2002 at 07:47:38AM -0500, Bill Davidsen wrote:

> On Fri, 15 Feb 2002, Simon Kirby wrote:
> 
> > On Thu, Feb 14, 2002 at 12:51:14PM -0800, Andrew Morton wrote:
> > Not sure if this is related, but I still can't get 2.4 or 2.5 kernels to
> > actually read and write at the same time during a large file copy between
> > two totally separate devices (eg: from hda1 to hdc1).  "vmstat 1" shows
> > reads with no writing for about 6-8 seconds followed by writes with no
> > reading for about 5-6 seconds, repeat.
> 
> You don't have enough memory... you can probably tune bdflush to make the
> system flush writes more aggressively, but one cause is that you fill all
> available memory before bdflush even runs. Try setting the time way down,
> say one sec, and see if things change.
> 
> Note that this may not make the system run faster in any significant way,
> it may just get all the drive lights blinking.

This is happening on boxes with 1 GB of memory, etc... Besides that,
bdflush's first argument is a percentage, and that's what I was
adjusting.  And yes, I've set the percentage way down and it has
increased the rate at which it switches back and forth to make it look
like it's reading and writing at the same time, but it's not.  Throughput
never goes up.

This sort of thing works fine in 2.2 kernels...

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

      reply	other threads:[~2002-02-17 16:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 16:03 fsync delays for a long time Alexander Moibenko
2002-02-14 17:39 ` Alan Cox
2002-02-14 20:51   ` Andrew Morton
2002-02-14 21:09     ` Alan Cox
2002-02-14 21:12       ` Alexander Moibenko
2002-02-14 21:37         ` Alan Cox
2002-02-14 21:26           ` Alexander Moibenko
2002-02-14 21:41             ` Andrew Morton
2002-02-14 22:18               ` Alexander Moibenko
2002-02-14 21:20       ` Andrew Morton
2002-02-14 21:38         ` Alan Cox
2002-02-15 16:48         ` Stephen C. Tweedie
2002-02-15 17:24     ` Simon Kirby
2002-02-15 19:07       ` Andrew Morton
2002-02-15 19:21         ` Simon Kirby
2002-02-17 12:47       ` Bill Davidsen
2002-02-17 16:45         ` Simon Kirby [this message]

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=20020217164531.GA19111@netnation.com \
    --to=sim@netnation.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