From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH rdma-next 0/5] Extend flow steering IPv4 and IPv6 specification.
Date: Sun, 28 Aug 2016 14:11:35 +0300 [thread overview]
Message-ID: <1472382700-30216-1-git-send-email-leon@kernel.org> (raw)
This patch set extends the IPv4 and IPv6 flow specification.
New fields in IPv4:
1. Type of Service
2. Time to Live
3. Flags
4. Protocol
New fields in IPv6:
1. Traffic Class
2. Flow Label
3. Next Header
4. Hop Limit
The first patch in this series adds support to extend the flow
steering specification. Previously, user flow specification
and kernel flow specification were must to be equal in their size.
To support extensions, we change the flow specifications conditions
test to be as following:
1. Every mask field that is given by the user and doesn't exist in
kernel is validated to be zero. Thus, new user-space would only fail
if it's using (i.e field_mask != 0) a field which doesn't exist in
the current kernel version.
2. All types are known by the kernel.
3. If the kernel is newer than the user-space, all fields (and by
that, their masks) weren't given by the user are assumed as zeros
and ignored.
4. The ABI declares filters as 32bit aligned. This is necessary to
avoid unaligned access when reading the header.
Available in the "topic/ext-flow" topic branch of this git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git
Or for browsing:
https://git.kernel.org/cgit/linux/kernel/git/leon/linux-rdma.git/log/?h=topic/ext-flow
Thanks,
Maor & Leon
Maor Gottlieb (5):
IB/core: Add support to extend flow steering specifications
IB/core: Add more fields to IPv4 flow specification
IB/core: Add more fields to IPv6 flow specification
IB/mlx5: Add support in TOS and protocol to flow steering
IB/mlx5: Add support of more IPv6 fields to flow steering
drivers/infiniband/core/uverbs_cmd.c | 102 ++++++++++++++++++++++++--------
drivers/infiniband/hw/mlx4/main.c | 25 ++++++++
drivers/infiniband/hw/mlx5/main.c | 110 ++++++++++++++++++++++++++++-------
include/rdma/ib_verbs.h | 23 ++++++++
include/uapi/rdma/ib_user_verbs.h | 13 ++++-
5 files changed, 226 insertions(+), 47 deletions(-)
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-08-28 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-28 11:11 Leon Romanovsky [this message]
[not found] ` <1472382700-30216-1-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-08-28 11:11 ` [PATCH rdma-next 1/5] IB/core: Add support to extend flow steering specifications Leon Romanovsky
[not found] ` <1472382700-30216-2-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-08-29 13:02 ` Sagi Grimberg
2016-08-28 11:11 ` [PATCH rdma-next 2/5] IB/core: Add more fields to IPv4 flow specification Leon Romanovsky
2016-08-28 11:11 ` [PATCH rdma-next 3/5] IB/core: Add more fields to IPv6 " Leon Romanovsky
[not found] ` <1472382700-30216-4-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-08-29 13:05 ` Sagi Grimberg
2016-08-28 11:11 ` [PATCH rdma-next 4/5] IB/mlx5: Add support in TOS and protocol to flow steering Leon Romanovsky
[not found] ` <1472382700-30216-5-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-08-29 13:08 ` Sagi Grimberg
2016-08-28 11:11 ` [PATCH rdma-next 5/5] IB/mlx5: Add support of more IPv6 fields " Leon Romanovsky
[not found] ` <1472382700-30216-6-git-send-email-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-08-29 13:09 ` Sagi Grimberg
2016-08-29 13:09 ` [PATCH rdma-next 0/5] Extend flow steering IPv4 and IPv6 specification Sagi Grimberg
[not found] ` <dc171c92-9c49-9a24-be1d-ac154d3f96d7-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2016-08-29 13:19 ` Leon Romanovsky
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=1472382700-30216-1-git-send-email-leon@kernel.org \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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