Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH 0/18] export operations rewrite
Date: Fri, 30 Mar 2007 13:34:53 +1000	[thread overview]
Message-ID: <17932.34141.590792.120454@notabene.brown> (raw)
In-Reply-To: message from Christoph Hellwig on Saturday March 17

On Saturday March 17, hch@infradead.org wrote:

less that 2 weeks later....

> This patchset is a medium scale rewrite of the export operations
> interface.  The goal is to make the interface less complex, and
> easier to understand from the filesystem side, aswell as preparing
> generic support for exporting of 64bit inode numbers.
> 
> This touches all nfs exporting filesystems, and I've done testing
> on all of the filesystems I have here locally (xfs, ext2, ext3, reiserfs,
> jfs)

My only question involves motivation.

  You say "less complex", but to me it just looks "different" - though
  being very familiar with the original, that might be a biased view.
  Can you say more about how it is less complex?
  Maybe the extension to generic 64bit support will make that clear...

  But then generic 64bit support should just be an independent set of
  helper functions that can be plugged in to the export_operations
  structure.

For what it does, the code looks fine, and I can see some definite
improvements here and there, but I'm not clear on the over-all
motivation.

Thanks,
NeilBrown

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-03-30  3:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-17  1:09 [PATCH 0/18] export operations rewrite Christoph Hellwig
2007-03-28 16:39 ` [NFS] " Christoph Hellwig
2007-03-30  3:34 ` Neil Brown [this message]
2007-05-01 10:39   ` Christoph Hellwig
2007-05-04  6:49     ` Neil Brown
2007-05-06 23:52       ` [NFS] " Neil Brown
2007-05-07  0:06         ` Neil Brown
2007-05-07  7:51           ` [NFS] " Christoph Hellwig
2007-05-13 20:41             ` Christoph Hellwig
2007-05-14  0:13               ` Neil Brown
2007-04-01 15:03 ` David Woodhouse
2007-05-13 20:43   ` [NFS] " Christoph Hellwig

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=17932.34141.590792.120454@notabene.brown \
    --to=neilb@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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