From: Jeff Lessem <Jeff.Lessem@Colorado.EDU>
To: linux-kernel@vger.kernel.org
Subject: Re: Writeout in recent kernels/VMs poor compared to last -ac
Date: Sat, 12 Jan 2002 13:47:45 -0700 [thread overview]
Message-ID: <200201122047.NAA50782@ibg.colorado.edu> (raw)
In-Reply-To: "Adam Kropelin"'s message of Sat, 12 Jan 2002 10:17:39 EST.
In-Reply-To: <009e01c19b7c$463457d0$02c8a8c0@kroptech.com>
In your message of: Sat, 12 Jan 2002 10:17:39 EST, you write:
>I recently began regularly transferring large (600 MB+) files to my
>Linux-based fileserver and have noticed what I would characterize as poor
>writeout behavior under this load. I've done a bit of comparison testing
>which may help reveal the problem better.
I see the same behavior when writing to a USB attached harddisk/MP3
player, which also is formated VFAT. Doing a cp *.mp3 /usbdrive/ will
read the mp3s into memory, until all free memory is filled, and then
start writing them to the usb drive. Because it can only write at
800KB/s this behavior is very noticable. Once the few hundred MB of
files in memory have been written out, the next batch of files will be
read into memory, and then written out.
This behavior occurs under 2.4.17, and has occured under all recent
2.4 kernels. I haven't done any rigorous testing to see which, if
any, -ac or early 2.4 kernels do not show this behavior.
If VFAT is considered an issue, I can reformat the disk ext2 for
testing.
Not really any new information to add, just a "me too", though I would
be happy to try out any proposed fixes.
--
Jeff Lessem.
prev parent reply other threads:[~2002-01-12 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 15:17 Adam Kropelin
2002-01-12 15:29 ` Adam Kropelin
2002-01-12 16:03 ` Rik van Riel
2002-01-12 16:30 ` Andrea Arcangeli
2002-01-12 18:19 ` Adam Kropelin
2002-01-12 18:49 ` Jussi Laako
2002-01-12 20:47 ` Jeff Lessem [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=200201122047.NAA50782@ibg.colorado.edu \
--to=jeff.lessem@colorado.edu \
--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®