From: Yongseok Koh <yskoh@mellanox.com>
To: Bin Huang <huangbin.mails@gmail.com>
Cc: nelio.laranjeiro@6wind.com, dev@dpdk.org,
adrien.mazarguil@6wind.com, bin.huang@hxt-semitech.com,
jie2.liu@hxt-semitech.com, bing.zhao@hxt-semitech.com,
zhiqiang.zhang@hxt-semitech.com
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add ptype table idx for TCP ACK packets
Date: Fri, 30 Mar 2018 10:22:18 -0700 [thread overview]
Message-ID: <20180330172216.GA26027@yongseok-MBP.local> (raw)
In-Reply-To: <1522386818-6838-1-git-send-email-huangbin.mails@gmail.com>
On Fri, Mar 30, 2018 at 01:13:38PM +0800, Bin Huang wrote:
> From: Bin Huang <bin.huang@hxt-semitech.com>
>
> 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%2Fwww.mail-archive.com%2Fusers%40dpdk.org%2Fmsg02980.html&data=02%7C01%7Cyskoh%40mellanox.com%7Ca4f58bc587d041482c9308d595fd16f7%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636579836609612796&sdata=wyfDNPG1EZQSzAyaWxfIfMnqjWZ9vdeLz1EZFzHx6Cw%3D&reserved=0
>
> Signed-off-by: Bin Huang <bin.huang@hxt-semitech.com>
Acked-by: Yongseok Koh <yskoh@mellanox.com>
Thank you!
next prev parent reply other threads:[~2018-03-30 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 5:13 Bin Huang
2018-03-30 17:22 ` Yongseok Koh [this message]
2018-04-01 7:44 ` Shahaf Shuler
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=20180330172216.GA26027@yongseok-MBP.local \
--to=yskoh@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=bin.huang@hxt-semitech.com \
--cc=bing.zhao@hxt-semitech.com \
--cc=dev@dpdk.org \
--cc=huangbin.mails@gmail.com \
--cc=jie2.liu@hxt-semitech.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=zhiqiang.zhang@hxt-semitech.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).