From: David Ahern <dsahern@gmail.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Leon Romanovsky <leonro@mellanox.com>,
netdev <netdev@vger.kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
RDMA mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH iproute2-next] rdma: Update device capabilities flags
Date: Thu, 8 Mar 2018 10:20:45 -0700 [thread overview]
Message-ID: <403074a9-b0fa-9042-76c3-bfa3042923c7@gmail.com> (raw)
In-Reply-To: <20180307090535.8986-1-leon@kernel.org>
On 3/7/18 2:05 AM, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> In kernel commit e1d2e8873369 ("IB/core: Add PCI write
> end padding flags for WQ and QP"), we introduced new
> device capability to advertise PCI write end padding.
>
> PCI write end padding is the device's ability to pad the ending of
> incoming packets (scatter) to full cache line such that the last
> upstream write generated by an incoming packet will be a full cache
> line.
>
> This commit updates RDMAtool to present this field.
>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> ---
> rdma/dev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/rdma/dev.c b/rdma/dev.c
> index 03ab8683..e2eafe47 100644
> --- a/rdma/dev.c
> +++ b/rdma/dev.c
> @@ -53,7 +53,8 @@ static const char *dev_caps_to_str(uint32_t idx)
> x(SG_GAPS_REG, 32) \
> x(VIRTUAL_FUNCTION, 33) \
> x(RAW_SCATTER_FCS, 34) \
> - x(RDMA_NETDEV_OPA_VNIC, 35)
> + x(RDMA_NETDEV_OPA_VNIC, 35) \
> + x(PCI_WRITE_END_PADDING, 36)
>
> enum { RDMA_DEV_FLAGS(RDMA_BITMAP_ENUM) };
>
>
applied to iproute2-next
prev parent reply other threads:[~2018-03-08 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 9:05 [PATCH iproute2-next] rdma: Update device capabilities flags Leon Romanovsky
2018-03-08 17:20 ` David Ahern [this message]
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=403074a9-b0fa-9042-76c3-bfa3042923c7@gmail.com \
--to=dsahern@gmail.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).