mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: GOTO Masanori <gotom@debian.or.jp>,
	davej@codemonkey.org.uk, davej@suse.de,
	linux-kernel@vger.kernel.org, andrea@suse.de, cel@monkey.org
Subject: Re: Possible O_DIRECT problems ?
Date: Fri, 21 Dec 2001 13:46:53 +0100	[thread overview]
Message-ID: <E16HP4f-0001di-00@charged.uio.no> (raw)
In-Reply-To: <20011221000806.A26849@suse.de> <20011221003942.B26268@codemonkey.org.uk> <w53ellp2out.wl@megaela.fe.dis.titech.ac.jp>
In-Reply-To: <w53ellp2out.wl@megaela.fe.dis.titech.ac.jp>

On Friday 21. December 2001 05:12, GOTO Masanori wrote:
> At Fri, 21 Dec 2001 00:39:42 +0000,
>
> Dave Jones <davej@codemonkey.org.uk> wrote:
> > On Fri, Dec 21, 2001 at 01:23:45AM +0100, Trond Myklebust wrote:
> >  >    O_DIRECT for NFS isn't yet merged into the kernel. Are these Chuck
> >  > Lever's NFS patches you've been testing?
>
> Where is Chuck's patch ? I searched but didn't find.

I haven't put it up on my own web-site, but it should be available from the 
CITI NFS client performance project site. See

   http://www.citi.umich.edu/projects/nfs-perf/patches/

> Supporting direct_IO with NFS is some meaningful
> for users who have fast NAS server environment, IMHO.

It can also provide for better data security in some circumstances. 
Journaling in databases over NFS can for instance benefit greatly, and has 
been one of Chuck's motivations for doing it.

Cheers,
   Trond

  parent reply	other threads:[~2001-12-21 12:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21  0:08 Dave Jones
2001-12-21  0:23 ` Trond Myklebust
2001-12-21  0:39   ` Dave Jones
     [not found]     ` <w53ellp2out.wl@megaela.fe.dis.titech.ac.jp>
2001-12-21 12:46       ` Trond Myklebust [this message]
2001-12-21 16:14         ` Chuck Lever
2001-12-21 16:04       ` Chuck Lever
2001-12-29 15:25     ` Andrea Arcangeli
2001-12-29 18:46       ` CJ
2001-12-30  5:39         ` Andre Hedrick
2001-12-30 11:16           ` Gérard Roudier

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=E16HP4f-0001di-00@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=andrea@suse.de \
    --cc=cel@monkey.org \
    --cc=davej@codemonkey.org.uk \
    --cc=davej@suse.de \
    --cc=gotom@debian.or.jp \
    --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®