From: Jens Axboe <axboe@suse.de>
To: Nathan Black <NBlack@md.aacisd.com>
Cc: "'bert hubert'" <ahu@ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: drive/block device write scheduling, buffer flushing?
Date: Wed, 31 Jan 2001 19:41:55 +0100 [thread overview]
Message-ID: <20010131194155.U508@suse.de> (raw)
In-Reply-To: <8FED3D71D1D2D411992A009027711D671880@md>
In-Reply-To: <8FED3D71D1D2D411992A009027711D671880@md>; from NBlack@md.aacisd.com on Wed, Jan 31, 2001 at 01:29:05PM -0500
On Wed, Jan 31 2001, Nathan Black wrote:
> That is what I wanted to do...Write directly to the disk. But the
> kernel(2.4.1) is caching the io...
Bind the block device to a /dev/raw* and do I/O on that
--
Jens Axboe
-
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 prev parent reply other threads:[~2001-01-31 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 18:29 drive/block device write scheduling, buffer flushing? Nathan Black
2001-01-31 18:41 ` Jens Axboe [this message]
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=20010131194155.U508@suse.de \
--to=axboe@suse.de \
--cc=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