From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
talal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH libibverbs 0/3] Scatter FCS support
Date: Mon, 6 Jun 2016 18:59:46 -0400 [thread overview]
Message-ID: <e204445a-1f37-2d4e-8658-e8f827ca21d8@redhat.com> (raw)
In-Reply-To: <1463662369-18395-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1425 bytes --]
On 5/19/2016 8:52 AM, Yishai Hadas wrote:
> Frame Check Sequence(FCS) is an error detecting code that terminates an
> Ethernet frame. When using Raw Ethernet, users sometimes want to
> validate the FCS themselves, and therefore it should be scattered to the
> receive buffers.
>
> This series adds the above support.
>
> The user can control scattering the FCS using Queue-Pair(QP) creation flag
> called IBV_QP_CREATE_SCATTER_FCS.
>
> Also, to report this new device capability, we had to add a new device
> capability flags in the uverbs response called device_cap_flags_ex, since all
> the current device_cap_flags are occupied.
>
> device_cap_flags_ex 0-31 bits are identical to the legacy device_cap_flags, and
> the upper 32 bits (32-63 bits) report new extended device capabilities.
>
> Devices that support scattering the FCS should report it in device_cap_flags_ex
> using IBV_DEVICE_RAW_SCATTER_FCS.
>
>
> Majd Dibbiny (3):
> Extend devinfo verbosity mode
> Add extended device capability flags
> Add SCATTER_FCS QP create flag
>
> examples/devinfo.c | 96 +++++++++++++++++++++++++++++++++++++++++++
> include/infiniband/kern-abi.h | 2 +
> include/infiniband/verbs.h | 8 ++++
> man/ibv_query_device_ex.3 | 1 +
> src/cmd.c | 13 +++++-
> 5 files changed, 119 insertions(+), 1 deletion(-)
>
Thanks, series applied.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2016-06-06 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 12:52 [PATCH libibverbs 0/3] Scatter FCS support Yishai Hadas
[not found] ` <1463662369-18395-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-05-19 12:52 ` [PATCH libibverbs 1/3] Extend devinfo verbosity mode Yishai Hadas
2016-05-19 12:52 ` [PATCH libibverbs 2/3] Add extended device capability flags Yishai Hadas
2016-05-19 12:52 ` [PATCH libibverbs 3/3] Add SCATTER_FCS QP create flag Yishai Hadas
2016-06-06 22:59 ` Doug Ledford [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=e204445a-1f37-2d4e-8658-e8f827ca21d8@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=talal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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