public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@clusterfs.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org, braam@clusterfs.com
Subject: Re: [0/9] Lustre VFS patches for 2.6
Date: Wed, 7 Jul 2004 21:20:24 +0300	[thread overview]
Message-ID: <20040707182024.GK5619@linuxhacker.ru> (raw)
In-Reply-To: <40EC19C6.9010309@comcast.net>

Hello!

On Wed, Jul 07, 2004 at 11:41:58AM -0400, John Richard Moser wrote:

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

These are just kernel bits necessary for Lustre to work.
Without lustre there should be no noticeable difference.
Lustre is a cluster filesystem and you can get more info about it at
http://www.lustre.org

Bye,
    Oleg

  reply	other threads:[~2004-07-07 18:22 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
2004-07-07 18:20   ` Oleg Drokin [this message]
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=20040707182024.GK5619@linuxhacker.ru \
    --to=green@clusterfs.com \
    --cc=braam@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.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