From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-rdma@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Shirley Ma <shirley.ma@oracle.com>,
Wendy Cheng <s.wendy.cheng@gmail.com>
Subject: Re: Proposal for simplifying NFS/RDMA client memory registration
Date: Mon, 3 Mar 2014 11:07:33 -0800 [thread overview]
Message-ID: <20140303190733.GA4556@infradead.org> (raw)
In-Reply-To: <E755E683-C064-4ED3-8448-C61F4E5AF16E@oracle.com>
On Mon, Mar 03, 2014 at 12:02:33PM -0500, Chuck Lever wrote:
> All HCAs in 3.13 (and rxe) can support either MTHCA_FMR or FRMR or both. Wendy?s HCA supports only ALLPHYSICAL.
Is Wendy planning to submit her HCA driver ASAP? If not there's not
reason to keep ALLPHYSICAL either.
> Does it make sense to deprecate then remove the registration modes in the first list?
Yes.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Shirley Ma <shirley.ma-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Wendy Cheng
<s.wendy.cheng-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: Proposal for simplifying NFS/RDMA client memory registration
Date: Mon, 3 Mar 2014 11:07:33 -0800 [thread overview]
Message-ID: <20140303190733.GA4556@infradead.org> (raw)
In-Reply-To: <E755E683-C064-4ED3-8448-C61F4E5AF16E-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
On Mon, Mar 03, 2014 at 12:02:33PM -0500, Chuck Lever wrote:
> All HCAs in 3.13 (and rxe) can support either MTHCA_FMR or FRMR or both. Wendy?s HCA supports only ALLPHYSICAL.
Is Wendy planning to submit her HCA driver ASAP? If not there's not
reason to keep ALLPHYSICAL either.
> Does it make sense to deprecate then remove the registration modes in the first list?
Yes.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-03 19:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:44 Proposal for simplifying NFS/RDMA client memory registration Chuck Lever
2014-02-26 16:44 ` Chuck Lever
2014-02-26 17:42 ` faibish, sorin
2014-02-26 17:42 ` faibish, sorin
2014-02-28 21:41 ` Tom Talpey
2014-02-28 21:41 ` Tom Talpey
[not found] ` <CABgxfbHwo13ma=-Xn+S36WwD8LVNLdw6UHztFe8EkCA_=NBenw@mail.gmail.com>
2014-02-28 22:26 ` Wendy Cheng
2014-02-28 22:26 ` Wendy Cheng
2014-03-01 2:59 ` Chuck Lever
2014-03-01 2:59 ` Chuck Lever
2014-03-01 16:00 ` Jeff Layton
2014-03-01 16:00 ` Jeff Layton
2014-03-01 17:14 ` Chuck Lever
2014-03-01 17:14 ` Chuck Lever
2014-03-01 21:29 ` Tom Tucker
2014-03-01 21:29 ` Tom Tucker
2014-03-02 22:28 ` Chuck Lever
2014-03-02 22:28 ` Chuck Lever
2014-03-03 17:02 ` Chuck Lever
2014-03-03 17:02 ` Chuck Lever
2014-03-03 19:07 ` Christoph Hellwig [this message]
2014-03-03 19:07 ` Christoph Hellwig
2014-03-03 19:54 ` faibish, sorin
2014-03-03 19:54 ` faibish, sorin
2014-03-03 20:33 ` Wendy Cheng
2014-03-03 20:33 ` Wendy Cheng
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=20140303190733.GA4556@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=s.wendy.cheng@gmail.com \
--cc=shirley.ma@oracle.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.