All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: tshibata@ab.jp.nec.com
Cc: linux-fsdevel@vger.kernel.org
Subject: NEC's GFS for mainline kernels?
Date: Tue, 28 Jan 2003 16:32:41 +0100	[thread overview]
Message-ID: <20030128163241.A7836@lst.de> (raw)

Hi Shibata-san,

is there a chance your team could release NEC's direct-to-SAN NFS code (*)
as a patch against stock kernels, too instead of only as part of the
kernel RPMs for NEC's IA64 servers?  The concept looks very nice, but I
think the integration with the scsi layer and the xfs/nfs code still
needs to be a lot cleaner which could benefit from some public review.

I was pretty suprised about GFS and some other interesting changes in
NEC's tree, it's a shame you hide such nice free software :)

	Christoph

(*) the name GFS clashes with another linux filesystem which is very
    confusing, btw..

             reply	other threads:[~2003-01-28 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 15:32 Christoph Hellwig [this message]
2003-01-28 16:34 ` NEC's GFS for mainline kernels? Trond Myklebust
2003-01-28 17:21   ` David Chow
2003-01-28 17:40     ` Trond Myklebust
2003-01-30 20:55   ` Christoph Hellwig
2003-01-30 15:07 ` Takashi Yanagawa

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=20030128163241.A7836@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tshibata@ab.jp.nec.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.