From: Shahaf Shuler <shahafs@mellanox.com>
To: Yuanhan Liu <yliu@fridaylinux.org>, Yongseok Koh <yskoh@mellanox.com>
Cc: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
Wisam Monther <wisamm@mellanox.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] A missing mlx5 patch for stable 17.11
Date: Tue, 29 May 2018 06:51:14 +0000 [thread overview]
Message-ID: <DB7PR05MB4426792F9BD28AF1002C0199C36D0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180527031547.debfexmbbuwsl77m@yuanhanliu-NB0.tencent.com>
Hi Yuanhan,
Sunday, May 27, 2018 6:16 AM, Yuanhan Liu:
> Subject: Re: A missing mlx5 patch for stable 17.11
>
> On Wed, May 23, 2018 at 09:07:56PM +0000, Yongseok Koh wrote:
> > Hi, Yuanhan
> >
> > There's one missing patch from upstream repo. It is because the patch
> > doesn't have Cc tag. I should've asked when I acked it.
> >
> > Please push this one to the 17.11 queue for the next available release.
> > I confirmed it can be applied without any conflict.
>
> Hi Yongseok,
>
> Thank you for letting me know that! I have now pushed it to dpdk-
> stable/17.11.
In fact there is a bunch of fixes that we plan to backport to 17.11. they are currently missing probably to rebase issues.
We will send them out by EOW.
Thanks.
>
> --yliu
> >
> >
> > commit 0915e287a6a7ed884a3de198f08926d8418366d4
> > Author: Bin Huang <bin.huang@hxt-semitech.com>
> > Date: Fri Mar 30 13:13:38 2018 +0800
> >
> > net/mlx5: add packet type index for TCP ack
> >
> > According to CQE format:
> > - l4_hdr_type:
> > 0 - None
> > 1 - TCP header was present in the packet
> > 2 - UDP header was present in the packet
> > 3 - TCP header was present in the packet with Empty
> > TCP ACK indication. (TCP packet <ACK> flag is set,
> > and packet carries no data)
> > 4 - TCP header was present in the packet with TCP ACK indication.
> > (TCP packet <ACK> flag is set, and packet carries data).
> >
> > A packet should be identified as TCP packet if l4_hdr_type is 1, 3 or 4.
> > Add corresponding idx of TCP ACK to ptype table.
> >
> > previous discussion:
> >
> >
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw
> ww
> > .mail-
> archive.com%2Fusers%40dpdk.org%2Fmsg02980.html&data=02%7C01%7Csh
> >
> ahafs%40mellanox.com%7C84449d300af3499abdfb08d5c3802afc%7Ca652971
> c7d2e
> >
> 4d9ba6a4d149256f461b%7C0%7C0%7C636629877612129429&sdata=Zqw10vw
> 38CRcKU
> > r0Jc25rM8ruEO7bP%2Fa5hHqOZ%2BB3EE%3D&reserved=0
> >
> > Signed-off-by: Bin Huang <bin.huang@hxt-semitech.com>
> > Acked-by: Yongseok Koh <yskoh@mellanox.com>
> >
> >
> >
> > Thanks,
> > Yongseok
next prev parent reply other threads:[~2018-05-29 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 21:07 Yongseok Koh
2018-05-27 3:15 ` Yuanhan Liu
2018-05-29 6:51 ` Shahaf Shuler [this message]
2018-06-02 5:14 ` Yuanhan Liu
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=DB7PR05MB4426792F9BD28AF1002C0199C36D0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=luca.boccassi@gmail.com \
--cc=stable@dpdk.org \
--cc=wisamm@mellanox.com \
--cc=yliu@fridaylinux.org \
--cc=yskoh@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).