From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Steve Wise <swise@opengridcomputing.com>, dledford@redhat.com
Cc: infinipath@intel.com, sagig@mellanox.com,
linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org,
bfields@fieldses.org
Subject: Re: [PATCH RESEND 0/4] Use max_sge_rd device capability
Date: Tue, 28 Jul 2015 12:28:43 +0300 [thread overview]
Message-ID: <55B74B4B.8000000@dev.mellanox.co.il> (raw)
In-Reply-To: <20150727230906.10102.88491.stgit@build2.ogc.int>
On 7/28/2015 2:09 AM, Steve Wise wrote:
> Resending because I forgot to cc linux-rdma :(
>
> Some devices were not setting this capability, so fix those devices,
> and svcrdma to use max_sge_rd. Also remove rdma_cap_read_multi_sge()
> since it isn't needed.
>
> These patches were originally part of:
>
> http://www.spinics.net/lists/linux-rdma/msg27436.html
>
> They really aren't part of iSER/iWARP at all, so I've split
> them out.
>
> Bruce: This hits svcrdma, but I suggest they get merged via Doug's tree
> to avoid any merge problems.
>
> ---
Looks good,
Reviewed-by: Sagi Grimberg <sagig@mellanox.com>
WARNING: multiple messages have this Message-ID (diff)
From: Sagi Grimberg <sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org
Subject: Re: [PATCH RESEND 0/4] Use max_sge_rd device capability
Date: Tue, 28 Jul 2015 12:28:43 +0300 [thread overview]
Message-ID: <55B74B4B.8000000@dev.mellanox.co.il> (raw)
In-Reply-To: <20150727230906.10102.88491.stgit-PBeJgSbIpn97NCTnQtmixQ@public.gmane.org>
On 7/28/2015 2:09 AM, Steve Wise wrote:
> Resending because I forgot to cc linux-rdma :(
>
> Some devices were not setting this capability, so fix those devices,
> and svcrdma to use max_sge_rd. Also remove rdma_cap_read_multi_sge()
> since it isn't needed.
>
> These patches were originally part of:
>
> http://www.spinics.net/lists/linux-rdma/msg27436.html
>
> They really aren't part of iSER/iWARP at all, so I've split
> them out.
>
> Bruce: This hits svcrdma, but I suggest they get merged via Doug's tree
> to avoid any merge problems.
>
> ---
Looks good,
Reviewed-by: Sagi Grimberg <sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" 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:[~2015-07-28 9:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 23:09 [PATCH RESEND 0/4] Use max_sge_rd device capability Steve Wise
2015-07-27 23:09 ` Steve Wise
2015-07-27 23:10 ` [PATCH RESEND 1/4] mlx4, mlx5, mthca: Expose max_sge_rd correctly Steve Wise
2015-07-27 23:10 ` Steve Wise
2015-07-27 23:10 ` [PATCH RESEND 2/4] ipath,qib: " Steve Wise
2015-07-27 23:10 ` Steve Wise
2015-07-27 23:10 ` [PATCH RESEND 3/4] svcrdma: Use max_sge_rd for destination read depths Steve Wise
2015-07-27 23:10 ` Steve Wise
2015-07-27 23:10 ` [PATCH RESEND 4/4] RDMA/Core: remove rdma_cap_read_multi_sge() helper Steve Wise
2015-07-27 23:10 ` Steve Wise
2015-07-27 23:17 ` [PATCH RESEND 0/4] Use max_sge_rd device capability Jason Gunthorpe
2015-07-27 23:17 ` Jason Gunthorpe
2015-07-28 5:44 ` ira.weiny
2015-07-28 5:44 ` ira.weiny
2015-07-28 9:28 ` Sagi Grimberg [this message]
2015-07-28 9:28 ` Sagi Grimberg
2015-07-28 13:42 ` J. Bruce Fields
2015-07-28 13:42 ` J. Bruce Fields
2015-07-28 14:45 ` Doug Ledford
2015-07-28 14:45 ` Doug Ledford
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=55B74B4B.8000000@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=bfields@fieldses.org \
--cc=dledford@redhat.com \
--cc=infinipath@intel.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagig@mellanox.com \
--cc=swise@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 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.