From: Bing Zhao <bingz@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] doc: add new feature for connection tracking
Date: Tue, 18 May 2021 13:49:05 +0000 [thread overview]
Message-ID: <CH0PR12MB5041AC9E440E0E51042C49C8D02C9@CH0PR12MB5041.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5133121.FE7OHWgHMe@thomas>
Thanks a lot to you all.
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, May 18, 2021 9:19 PM
> To: Bing Zhao <bingz@nvidia.com>; Ferruh Yigit
> <ferruh.yigit@intel.com>
> Cc: Ori Kam <orika@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> andrew.rybchenko@oktetlabs.ru
> Subject: Re: [PATCH] doc: add new feature for connection tracking
>
> External email: Use caution opening links or attachments
>
>
> 18/05/2021 15:16, Ferruh Yigit:
> > On 5/18/2021 1:52 PM, Bing Zhao wrote:
> > > The feature support of connection tracking is added in the
> feature
> > > table of networking drivers. The feature overview part is also
> > > updated.
> > >
> > > Signed-off-by: Bing Zhao <bingz@nvidia.com>
> >
> > Hi Bing,
> >
> > Thomas is suggestion another table to list flow API item/actions
> in
> > separate table, can this change can be replaced by it?
>
> Correct, I am adding conntrack as part of rte_flow features table.
> Please don't add it in the global table.
>
next prev parent reply other threads:[~2021-05-18 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 12:52 Bing Zhao
2021-05-18 13:16 ` Ferruh Yigit
2021-05-18 13:18 ` Thomas Monjalon
2021-05-18 13:49 ` Bing Zhao [this message]
2021-05-18 13:33 ` Bing Zhao
2021-05-18 13:44 ` Thomas Monjalon
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=CH0PR12MB5041AC9E440E0E51042C49C8D02C9@CH0PR12MB5041.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).