From: Larry McVoy <lm@bitmover.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: trond.myklebust@fys.uio.no, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.22 Give us today our daily wart...
Date: Thu, 10 Jul 2003 08:34:56 -0700 [thread overview]
Message-ID: <20030710153456.GB27605@work.bitmover.com> (raw)
In-Reply-To: <3F0C9D45.2020308@pobox.com>
On Wed, Jul 09, 2003 at 06:55:01PM -0400, Jeff Garzik wrote:
> Looks good to me...
I'm not sure that you care but this is completely incompatible with the
direct I/O extension that I did in IRIX's NFS, which was the first
direct I/O NFS implementation anywhere. The IRIX approach was to use
a different code path, direct I/O went through a TCP socket which was
carefully managed so that page flipping would work. If you want to
know the details I can dig them up but unless you are going down the
page flipping route, this looks fine.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2003-07-10 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 22:14 [PATCH] 2.4.22 Give us today our daily wart Trond Myklebust
2003-07-09 22:55 ` Jeff Garzik
2003-07-10 15:34 ` Larry McVoy [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=20030710153456.GB27605@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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