All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: tshibata@ab.jp.nec.com, linux-fsdevel@vger.kernel.org
Subject: Re: NEC's GFS for mainline kernels?
Date: Thu, 30 Jan 2003 21:55:33 +0100	[thread overview]
Message-ID: <20030130215533.A26221@lst.de> (raw)
In-Reply-To: <shsisw92pyu.fsf@charged.uio.no>; from trond.myklebust@fys.uio.no on Tue, Jan 28, 2003 at 05:34:17PM +0100

On Tue, Jan 28, 2003 at 05:34:17PM +0100, Trond Myklebust wrote:
> >>>>> " " == Christoph Hellwig <hch@lst.de> writes:
> 
>      > 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?
> 
> Hi,
> 
> Is that some variant on the RDMA concept? (see http://www.rdmaconsortium.org)
> 
> If so, please note that there is an ongoing effort to standardize
> RDMA-over-TCP via the IETF, and (of course) a parallel effort to
> integrate it into a future minor revision of NFSv4 (see
> http://www.snia.org/tech_activities/workgroups/nfs_rdma)

No, it doesn't go over the network but directly to fibrechannel.
See the diff (2.4.18 plain -> 2.4.18 nec) that I've put on nl.linux.org:

	http://nl.linux.org/~hch/patch-2.4.18-nec3.2.bz2


  parent reply	other threads:[~2003-01-30 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 15:32 NEC's GFS for mainline kernels? Christoph Hellwig
2003-01-28 16:34 ` Trond Myklebust
2003-01-28 17:21   ` David Chow
2003-01-28 17:40     ` Trond Myklebust
2003-01-30 20:55   ` Christoph Hellwig [this message]
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=20030130215533.A26221@lst.de \
    --to=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --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.