public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Richard Moser <nigelenki@comcast.net>
To: Oleg Drokin <green@clusterfs.com>
Cc: linux-kernel@vger.kernel.org, braam@clusterfs.com
Subject: Re: [0/9] Lustre VFS patches for 2.6
Date: Wed, 07 Jul 2004 11:41:58 -0400	[thread overview]
Message-ID: <40EC19C6.9010309@comcast.net> (raw)
In-Reply-To: <20040707124732.GA25877@clusterfs.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Interesting, but what exactly does this do?  Extra performance?  How?
Extra security?  Avoid deadlocks?

I'm not the kind of guy that just looks into a patch and claims to
understand all.  :)

Oleg Drokin wrote:
| Hello!
|
|    Following this mail, there are nine patches necessary for Lustre
support
|    in 2.6. The patches are against latest 2.6 bk snapshot.
|    Compared to previous sets of patches, this one does not change existing
|    structure and field names therefore leaving kernel VFS API
completely intact.
|    Also raw operations approach is changed, extra inode operation is
introduced
|    that is supposed to be called at the end of parent lookup and do
necessary
|    operations, if possible.
|    Of course it would be great if these patches would be included into the
|    kernel right away (and that is one of the reasons this set of patches
|    keeps old API intact). Also there were at least some interest in
some of the
|    patches from other parties (e.g. Trond Myklebust was interested in some
|    intent changes as I remember) and we are ready to work with those
so that
|    the patches will suit their needs as well.
|
| Bye,
|     Oleg
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at  http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at  http://www.tux.org/lkml/
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA7BnFhDd4aOud5P8RAhiGAKCJJUqqL9aylG8hkfCAD4GpfMYK+wCdHIj6
njpYVufE205L7MFz04ysdI4=
=tDnN
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-07-07 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-07 12:47 [0/9] Lustre VFS patches for 2.6 Oleg Drokin
2004-07-07 12:56 ` Christoph Hellwig
2004-07-07 15:14   ` Oleg Drokin
2004-07-07 15:17     ` Christoph Hellwig
2004-07-07 15:41 ` John Richard Moser [this message]
2004-07-07 18:20   ` Oleg Drokin
2004-07-07 17:34 ` Lars Marowsky-Bree

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=40EC19C6.9010309@comcast.net \
    --to=nigelenki@comcast.net \
    --cc=braam@clusterfs.com \
    --cc=green@clusterfs.com \
    --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