From: Nathan Black <NBlack@md.aacisd.com>
To: "'bert hubert'" <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org
Subject: RE: drive/block device write scheduling, buffer flushing?
Date: Wed, 31 Jan 2001 13:29:05 -0500 [thread overview]
Message-ID: <8FED3D71D1D2D411992A009027711D671880@md> (raw)
That is what I wanted to do...Write directly to the disk. But the
kernel(2.4.1) is caching the io...
-----Original Message-----
From: bert hubert [mailto:ahu@ds9a.nl]
Sent: Wednesday, January 31, 2001 12:51 PM
To: Nathan Black
Cc: linux-kernel@vger.kernel.org
Subject: Re: drive/block device write scheduling, buffer flushing?
On Wed, Jan 31, 2001 at 11:52:25AM -0500, Nathan Black wrote:
> I was wondering if there is a way to make the kernel write to disk faster.
> I need to maintain a 10 MB /sec write rate to a 10K scsi disk in a
computer,
> but it caches and doesn't start writing to disk until I hit about 700 MB.
At
> that point, it pauses(presumably while the kernel is flushing some of the
> buffers) and I will have missed data that I am trying to capture.
try opening with O_SYNC, or call fsync() every once in a while. Otherwise,
this sounds like an application for a raw device, whereby you can write
directly to the disk, with no caching in between.
Regards,
bert
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-31 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 18:29 Nathan Black [this message]
2001-01-31 18:41 ` Jens Axboe
2001-01-31 18:48 ` how to use and get raw devices bert hubert
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 16:52 drive/block device write scheduling, buffer flushing? Nathan Black
2001-01-31 17:51 ` bert hubert
2001-02-01 8:56 ` Rogier Wolff
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=8FED3D71D1D2D411992A009027711D671880@md \
--to=nblack@md.aacisd.com \
--cc=ahu@ds9a.nl \
--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®