From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Critical fixes for next-net-mlx
Date: Thu, 24 May 2018 17:56:02 +0100 [thread overview]
Message-ID: <302b6f86-b1bb-663e-b03a-92ae370d6480@intel.com> (raw)
In-Reply-To: <DB7PR05MB44266C6386490D9A1DD1902DC36A0@DB7PR05MB4426.eurprd05.prod.outlook.com>
On 5/24/2018 3:11 PM, Shahaf Shuler wrote:
> Hi Ferruh,
>
> In next-net-mlx and for “next-net” there are several critical fixes:
> * fecb5cb net/mlx4: drop support in Mellanox OFED 4.2
> Small doc update to notify all users – this is for next-net.
Documentation patches are accepted for rc6, ok for this one.
> * 995b985 net/mlx5: fix generic tunnel offloading compatibility
> check
> w/o it we cannot compile on RH7.5 with inbox libs (rdma-core).
This is updating Makefile, changing the data structure to check to give a
configuration decision. What to check has been updated because of what is
available in a distro.
I believe this is not something to break the build, and should be safe for rest
of the dpdk.
But from your point of view, if this data structure cause any un-expected result
in any other distro, you won't have another opportunity to fix, I just want to
confirm are you sure about change?
> * 8276073 net/mlx5: fix SW parser
> offset
> w/o it TSO for tunnel is broken
What is the scope of this one? Commit log doesn't have enough information. What
feature is broken, what is the exposure is it broken for all use cases or for
some, is there any workaround?
>
> Hope it will be possible to include those.
>
> --Shahaf
next prev parent reply other threads:[~2018-05-24 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 14:11 Shahaf Shuler
2018-05-24 16:56 ` Ferruh Yigit [this message]
2018-05-24 18:55 ` Shahaf Shuler
2018-05-25 8:45 ` Ferruh Yigit
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=302b6f86-b1bb-663e-b03a-92ae370d6480@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@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).