From: Daniel Phillips <phillips@bonn-fries.net>
To: otto.wyss@bluewin.ch,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Why don't have bits the same rights as humans! (flushing to disk waiting time)
Date: Sat, 25 Aug 2001 03:00:07 +0200 [thread overview]
Message-ID: <20010825005328Z16138-32383+1259@humbolt.nl.linux.org> (raw)
In-Reply-To: <3B802B68.ADA545DB@bluewin.ch>
In-Reply-To: <3B802B68.ADA545DB@bluewin.ch>
On August 19, 2001 11:11 pm, Otto Wyss wrote:
> I recently wrote some small files to the floppy disk and noticed almost nothing
> happened immediately but after a certain time the floppy actually started
> writing. So this action took more than 30 seconds instead just a few. This
> remembered me of the elevator problem in the kernel. To transfer this example
> into real live: A person who wants to take the elevator has to wait 8 hours
> before the elevator even starts. While probably everyone agrees this is
> ridiculous in real live astonishingly nobody complains about it in case of a disk.
My early flush patch, posted a month or so ago, takes care of this nicely.
I'm just waiting for 2.5 to roll around to do some more work on it.
> [...]
> Could anybody produce any real figures to prove/disprove my theory? Could
> anybody benchmark the disk access for the 3 waiting times (0, 200ms 30sec) with
> different loads?
Your theory is correct. I implemented the idea, took measurements, and found
dramatic performance improvements under some loads, while getting worse on
none. You can search lwn.net for a nice writeup by Jonathan Corbett.
--
Daniel
prev parent reply other threads:[~2001-08-25 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 21:11 Otto Wyss
2001-08-19 21:24 ` Ignacio Vazquez-Abrams
2001-08-19 22:16 ` David Ford
2001-08-19 22:36 ` Jakob Østergaard
2001-08-19 22:42 ` Kip Macy
2001-08-20 11:35 ` Helge Hafting
2001-08-25 0:04 ` Dr. Kelsey Hudson
2001-08-25 1:00 ` Daniel Phillips [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=20010825005328Z16138-32383+1259@humbolt.nl.linux.org \
--to=phillips@bonn-fries.net \
--cc=linux-kernel@vger.kernel.org \
--cc=otto.wyss@bluewin.ch \
/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®