mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: hch@infradead.org
Cc: "Peter J. Braam" <braam@clusterfs.com>,
	torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
	"'Phil Schwan'" <phil@clusterfs.com>
Subject: Re: [PATCH/RFC] Lustre VFS patch
Date: Mon, 24 May 2004 15:44:44 +0200	[thread overview]
Message-ID: <1085406284.2780.13.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040524120858.GE26863@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]

On Mon, 2004-05-24 at 14:08, hch@infradead.org wrote:
> > vfs-raw_ops-vanilla-2.6.patch
> > 
> >   This adds raw operations for setattr, mkdir, rmdir, mknod, unlink,
> >   symlink, link and rename.  The raw operations look up the parent
> >   directories (but not leaf nodes) involved in the operation and then
> >   ask the file system to execute the operation.  These methods allow
> >   us to delegate the execution of these functions to the server, and
> >   instantiate no dentries for leaf nodes, leaf nodes will only enter
> >   the dcache on subsequent lookups.  This patch dramatically
> >   simplifies the client/server lock management, particularly for
> >   rename.
> >  
> >   In Ottawa Linus suggested that we could maybe do this with intents
> >   instead.  I feel that both are ugly, both are possible but intents
> >   looked akward.
> 
> 
> This is complete crap.  We don't want to methods for every namespace
> operation.  

fun question: how does it deal with say a rename that would span mounts
on the client but wouldn't on the server? :)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-24 13:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 11:39 Peter J. Braam
2004-05-24 11:46 ` Jens Axboe
2004-05-25  1:48   ` braam
2004-05-25  6:47     ` Jens Axboe
2004-05-25  8:21       ` braam
2004-05-25  8:27         ` Jens Axboe
2004-05-25 10:52         ` Lars Marowsky-Bree
2004-05-25 11:45           ` braam
2004-05-25 13:35           ` Kevin Corry
2004-05-25 13:55             ` Jens Axboe
2004-05-24 12:00 ` hch
2004-05-24 12:01 ` hch
2004-05-24 12:03 ` hch
2004-05-24 15:33   ` Horst von Brand
2004-05-25 20:43     ` hch
2004-05-24 12:05 ` hch
2004-05-24 18:06   ` Trond Myklebust
2004-05-25  8:21     ` braam
2004-05-24 12:08 ` hch
2004-05-24 13:44   ` Arjan van de Ven [this message]
2004-05-24 13:53     ` viro
2004-05-28 16:56     ` braam
2004-05-28 17:00       ` Christoph Hellwig
2004-05-24 14:19 ` viro
2004-05-28 23:18 ` Maneesh Soni
2004-05-29 17:53 ` Anton Blanchard

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=1085406284.2780.13.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=akpm@osdl.org \
    --cc=braam@clusterfs.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@clusterfs.com \
    --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®