linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: BenHanokh Gabriel <gabriel@SANgate.com>
Cc: linux-mm@kvack.org
Subject: Re: non-buffers writes
Date: Mon, 14 Aug 2000 09:16:06 +0100	[thread overview]
Message-ID: <20000814091606.I12218@redhat.com> (raw)
In-Reply-To: <3986D82A.CF9DEE2A@SANgate.com>; from gabriel@SANgate.com on Tue, Aug 01, 2000 at 05:01:14PM +0300

Hi,

On Tue, Aug 01, 2000 at 05:01:14PM +0300, BenHanokh Gabriel wrote:
> 
> how can i do direct writes to disk without the buffer-cache overhead?
> i failed to see any relevant flag to open() , nor any fnctl()

Via /dev/raw/raw* raw devices ("man raw").  We plan much more powerful
direct IO functionality for 2.5 (which should support O_DIRECT opening
of devices and regular files), but for now raw IO is the only
supported mechanism.

Cheers, 
 Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

      reply	other threads:[~2000-08-14  8:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-01 14:01 BenHanokh Gabriel
2000-08-14  8:16 ` Stephen C. Tweedie [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=20000814091606.I12218@redhat.com \
    --to=sct@redhat.com \
    --cc=gabriel@SANgate.com \
    --cc=linux-mm@kvack.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