linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tom Talpey <tom@talpey.com>, Chuck Lever <chuck.lever@oracle.com>,
	linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org,
	Sagi Grimberg <sagig@mellanox.com>
Subject: Re: Future of FMR support, was: Re: [PATCH v1 5/9] xprtrdma: Add ro_unmap_sync method for FMR
Date: Wed, 25 Nov 2015 09:09:20 -0800	[thread overview]
Message-ID: <5655EB40.8070508@oracle.com> (raw)
In-Reply-To: <20151125090009.GA11255@infradead.org>

On 11/25/2015 1:00 AM, Christoph Hellwig wrote:
> On Tue, Nov 24, 2015 at 01:54:02PM -0800, santosh shilimkar wrote:
>> As already indicated to Sagi [1], RDS IB FR support is work in
>> progress and I was hoping to get it ready for 4.5. There are few
>> issues we found with one of the HCA and hence the progress
>> slowed down. Looking at where we are, 4.6 merge window seems
>> to be realistic for me to get RDS FR support.
>
> Ok.
>
>> Now on the iWARP transport itself, it has been bit tough because
>> of lack of hardware to tests. I have been requesting test(s) in
>> previous RDS patches and haven't seen any interest so far. If
>> this continues to be the trend, I might as well get rid of
>> RDS iWARP support after couple of merge windows.
>
> I'd say drop the current iWarp transport if it's not testable.  The
> only real difference between IB and iWarp is the needed to create
> a MR for the RDMA READ sink, and we're much better of adding that into
> the current IB transport if new iWarp users show up.

Agree. I will probably do it along with RDS IB FR support in 4.6

Regards,
Santosh

  reply	other threads:[~2015-11-25 17:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 22:13 [PATCH v1 0/9] NFS/RDMA client patches for 4.5 Chuck Lever
2015-11-23 22:13 ` [PATCH v1 1/9] xprtrdma: Add a safety margin for receive buffers Chuck Lever
2015-11-24  0:55   ` Tom Talpey
2015-11-24  1:16     ` Chuck Lever
2015-11-24  1:22       ` Tom Talpey
2015-11-24  1:44         ` Chuck Lever
2015-11-23 22:14 ` [PATCH v1 2/9] xprtrdma: Move struct ib_send_wr off the stack Chuck Lever
2015-11-23 22:14 ` [PATCH v1 3/9] xprtrdma: Introduce ro_unmap_sync method Chuck Lever
2015-11-24  6:45   ` Christoph Hellwig
2015-11-24  7:28     ` Jason Gunthorpe
2015-11-24 10:59     ` Sagi Grimberg
2015-11-24 13:43       ` Tom Talpey
2015-11-24 14:40         ` Sagi Grimberg
2015-11-24 14:39       ` Chuck Lever
2015-11-24 14:44         ` Sagi Grimberg
2015-11-24 15:20           ` Chuck Lever
2015-11-24 18:57         ` Jason Gunthorpe
2015-11-23 22:14 ` [PATCH v1 4/9] xprtrdma: Add ro_unmap_sync method for FRWR Chuck Lever
2015-11-23 22:14 ` [PATCH v1 5/9] xprtrdma: Add ro_unmap_sync method for FMR Chuck Lever
2015-11-24  0:57   ` Tom Talpey
2015-11-24  6:52     ` Future of FMR support, was: " Christoph Hellwig
2015-11-24  7:12       ` Jason Gunthorpe
2015-12-01 15:33         ` Chuck Lever
2015-12-02 12:27           ` Christoph Hellwig
2015-11-24 12:36       ` Tom Talpey
2015-11-24 21:54       ` santosh shilimkar
2015-11-25  9:00         ` Christoph Hellwig
2015-11-25 17:09           ` santosh shilimkar [this message]
2015-11-25 18:22             ` Or Gerlitz
2015-11-25 19:17               ` santosh shilimkar
2015-11-25 19:28             ` Jason Gunthorpe
2015-11-26 10:01               ` Sagi Grimberg
2015-11-23 22:14 ` [PATCH v1 6/9] xprtrdma: Add ro_unmap_sync method for all-physical registration Chuck Lever
2015-11-23 22:14 ` [PATCH v1 7/9] SUNRPC: Introduct xprt_commit_rqst() Chuck Lever
2015-11-24 19:54   ` Anna Schumaker
2015-11-24 19:56     ` Chuck Lever
2015-11-23 22:14 ` [PATCH v1 8/9] xprtrdma: Invalidate in the RPC reply handler Chuck Lever
2015-11-24  1:01   ` Tom Talpey
2015-11-23 22:15 ` [PATCH v1 9/9] xprtrdma: Revert commit e7104a2a9606 ('xprtrdma: Cap req_cqinit') Chuck Lever

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=5655EB40.8070508@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sagig@mellanox.com \
    --cc=tom@talpey.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).