From: Raslan Darawsheh <rasland@mellanox.com>
To: Eli Britstein <elibr@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>, Ori Kam <orika@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
Eli Britstein <elibr@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH V2 0/2] net/mlx5: optimize performance for IPv4/IPv6
Date: Mon, 4 May 2020 10:54:18 +0000 [thread overview]
Message-ID: <AM0PR05MB67075F9AD2DFF791AFDE0162C2A60@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200503104755.19545-1-elibr@mellanox.com>
Hi,
> -----Original Message-----
> From: Eli Britstein <elibr@mellanox.com>
> Sent: Sunday, May 3, 2020 1:48 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>; Ori Kam <orika@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Eli Britstein <elibr@mellanox.com>
> Subject: [PATCH V2 0/2] net/mlx5: optimize performance for IPv4/IPv6
>
> The HW is optimized for IPv4/IPv6. For such cases avoid matching on
> ethertype, and use ip_version field instead.
>
> Eli Britstein (2):
> net/mlx5: introduce a helper to set IP version match
> net/mlx5: optimize performance for IPv4/IPv6 ethertype
>
> drivers/net/mlx5/mlx5_flow_dv.c | 91
> +++++++++++++++++++++++++++++++----------
> 1 file changed, 69 insertions(+), 22 deletions(-)
>
> --
> 2.14.5
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-05-04 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 10:47 Eli Britstein
2020-05-03 10:47 ` [dpdk-dev] [PATCH V2 1/2] net/mlx5: introduce a helper to set IP version match Eli Britstein
2020-05-03 10:47 ` [dpdk-dev] [PATCH V2 2/2] net/mlx5: optimize performance for IPv4/IPv6 ethertype Eli Britstein
2020-05-03 11:34 ` [dpdk-dev] [PATCH V2 0/2] net/mlx5: optimize performance for IPv4/IPv6 Matan Azrad
2020-05-04 10:54 ` Raslan Darawsheh [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=AM0PR05MB67075F9AD2DFF791AFDE0162C2A60@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=elibr@mellanox.com \
--cc=matan@mellanox.com \
--cc=orika@mellanox.com \
--cc=viacheslavo@mellanox.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).