From: Tim Gardner <tim.gardner@canonical.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
linux-kernel@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>,
"David S. Miller" <davem@davemloft.net>, Tom Tucker <tom@ogc.us>,
Haggai Eran <haggaie@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Shani Michaeli <shanim@mellanox.com>,
linux-nfs@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH linux-next v3] SUNRPC: rpcrdma_register_default_external: Dynamically allocate ib_phys_buf
Date: Mon, 11 Mar 2013 20:53:18 -0600 [thread overview]
Message-ID: <513E989E.8060206@canonical.com> (raw)
In-Reply-To: <513E6271.3060107@opengridcomputing.com>
On 03/11/2013 05:02 PM, Tom Tucker wrote:
> On 3/11/13 4:25 PM, J. Bruce Fields wrote:
<snip>
>> Looks good to me; wish we could get it tested....
>
> I will test it. Tim could you please send me a final version that you'd
> like tested as a single message?
>
I'm a little confused about what you are asking. I think v3 of the patch
is the final version (unless you find bugs with it).
> Would someone (like Tim maybe ... hint hint) look at tearing out all
> those dead registration strategies? I don't think we need or will ever
> use bounce-buffers, memory windows, or mlnx fmr. The only two that are
> used and tested are all-phys and FRMR (the default).
>
Dunno if I'll get time for that. I had a one day window where I could
hack out some simple patches. Now I'm back to the usual grindstone.
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2013-03-12 2:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 15:39 [PATCH linux-next] SUNRPC: rpcrdma_register_default_external: Dynamically allocate ib_phys_buf Tim Gardner
[not found] ` <1362929953-63785-1-git-send-email-tim.gardner-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-03-10 17:16 ` Tom Tucker
2013-03-10 18:20 ` Tim Gardner
2013-03-10 20:28 ` J. Bruce Fields
[not found] ` <20130310202838.GL31448-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-03-11 17:37 ` [PATCH linux-next v2] " Tim Gardner
[not found] ` <1363023447-22453-1-git-send-email-tim.gardner-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-03-11 18:14 ` J. Bruce Fields
[not found] ` <20130311181450.GC30618-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-03-11 18:51 ` Tim Gardner
2013-03-11 19:15 ` J. Bruce Fields
[not found] ` <20130311191545.GA642-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-03-11 19:48 ` Myklebust, Trond
[not found] ` <4FA345DA4F4AE44899BD2B03EEEC2FA9286BA156-UCI0kNdgLrHLJmV3vhxcH3OR4cbS7gtM96Bgd4bDwmQ@public.gmane.org>
2013-03-11 20:00 ` J. Bruce Fields
2013-03-11 21:15 ` [PATCH linux-next v3] " Tim Gardner
[not found] ` <1363036508-24935-1-git-send-email-tim.gardner-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-03-11 21:25 ` J. Bruce Fields
[not found] ` <20130311212535.GG642-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-03-11 23:02 ` Tom Tucker
2013-03-12 2:53 ` Tim Gardner [this message]
[not found] ` <513E989E.8060206-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-03-12 3:40 ` Tom Tucker
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=513E989E.8060206@canonical.com \
--to=tim.gardner@canonical.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=haggaie@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=shanim@mellanox.com \
--cc=tom@ogc.us \
--cc=tom@opengridcomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).