From: Torben Frey <kernel@mailsammler.de>
To: Nuno Silva <nuno.silva@vgertech.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Horrible drive performance under concurrent i/o jobs (dlh problem?)
Date: Fri, 27 Dec 2002 14:04:57 +0100 [thread overview]
Message-ID: <3E0C4FF9.1010100@mailsammler.de> (raw)
In-Reply-To: <3E0276B9.40001@vgertech.com>
Hi Nuno,
> AFAIK, this is because you have some GB of memory (RAM) that are beeing
> used as disk-cache. It took 22 seconds for the cached writes-to-disk
> being flushed to the device.
Yes, I guess you are right...must be the flushing of my buffers, altogether it writes out
exactly the amount of data I would expect (the "22seconds block" included).
Regards,
Torben
PS: Sorry for my long delay, but I was at home over Xmas and could not reply earlier.
next prev parent reply other threads:[~2002-12-27 12:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 14:29 Horrible drive performance under concurrent i/o jobs (dlh problem?) Torben Frey
2002-12-20 1:47 ` Nuno Silva
2002-12-27 13:04 ` Torben Frey [this message]
2002-12-20 14:27 ` Roger Larsson
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 21:10 Con Kolivas
2002-12-18 22:16 ` Torben Frey
2002-12-18 22:37 ` Andrew Morton
2002-12-18 23:30 ` Torben Frey
2002-12-18 23:46 ` Andrew Morton
2002-12-18 22:40 ` Torben Frey
2002-12-18 19:06 Torben Frey
2002-12-20 20:40 ` Joseph D. Wagner
2002-12-20 22:25 ` David Lang
2002-12-21 6:00 ` Joseph D. Wagner
2002-12-23 1:29 ` David Lang
2002-12-24 9:18 ` Roy Sigurd Karlsbakk
2002-12-24 17:21 ` jw schultz
2002-12-24 21:00 ` Jeremy Fitzhardinge
2002-12-25 1:34 ` Rik van Riel
2002-12-25 2:02 ` jw schultz
2002-12-25 3:41 ` Barry K. Nathan
2002-12-23 17:48 ` Krzysztof Halasa
2002-12-23 18:13 ` Denis Vlasenko
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=3E0C4FF9.1010100@mailsammler.de \
--to=kernel@mailsammler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.com \
/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