mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
	nfsv4@linux-nfs.org
Subject: Re: [NFS] [GIT] NFS client update for 2.6.16
Date: Tue, 21 Mar 2006 14:06:20 -0500	[thread overview]
Message-ID: <1142967981.7987.92.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060321185734.GB19125@infradead.org>

On Tue, 2006-03-21 at 18:57 +0000, Christoph Hellwig wrote:
> On Tue, Mar 21, 2006 at 01:08:52PM -0500, Trond Myklebust wrote:
> > We never had support for multiple iovecs in O_DIRECT, but were passing
> > around a single iovec entry deep into code that couldn't care less.
> 
> anthing that moves from iovecs back to plain buffers is counterproductive.
> The plan is that every fullblown fs will only deal with iovecs, onlt drivers
> and synthetic filesystems will implement the plain buffers.

You need to do more than just add an iovec argument to
nfs_file_direct_read()/nfs_file_direct_write() if you want to achieve
this. The new call interface actually just clarifies something that was
implicit in the old one.

As I said in my other posting, I believe Chuck's changes are relatively
orthogonal to what you want to do: they neither make the low-level
plumbing better or worse for readv()/writev().

We'd be happy to work with you in the run-up to 2.6.18 to add
multi-segment support for the existing patchsets. It makes more sense to
me to append that functionality to the existing patchsets rather than
trigger a complete rewrite (and thus have a sh_tload more code to
retest).

Cheers,
    Trond


  reply	other threads:[~2006-03-21 19:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-21 17:11 Trond Myklebust
2006-03-21 17:46 ` [NFS] " Christoph Hellwig
2006-03-21 18:03   ` Chuck Lever
2006-03-21 18:55     ` Christoph Hellwig
2006-03-21 18:08   ` Trond Myklebust
2006-03-21 18:57     ` Christoph Hellwig
2006-03-21 19:06       ` Trond Myklebust [this message]
2006-03-21 19:12         ` Chuck Lever
2006-03-22 10:30           ` Christoph Hellwig
2006-03-22 11:35             ` Trond Myklebust
2006-03-21 18:58   ` Trond Myklebust
2006-03-22 10:25     ` Christoph Hellwig
2006-03-21 17:50 ` Jeff Garzik
2006-03-21 18:12   ` Trond Myklebust

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=1142967981.7987.92.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.org \
    --cc=torvalds@osdl.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®