From: Thomas Monjalon <thomas@monjalon.net>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [RFC] ethdev: introduce copy_field rte flow action
Date: Tue, 05 Jan 2021 23:18:46 +0100 [thread overview]
Message-ID: <9148098.Iffu9yAPz8@thomas> (raw)
In-Reply-To: <BN7PR12MB270749F71D1227EC33255990AFD10@BN7PR12MB2707.namprd12.prod.outlook.com>
05/01/2021 23:12, Alexander Kozyrev:
> Happy New Year Gentlemen, would you mind to share your thought on the proposed changes?
> I was thinking about renaming it to more general "copy item" to cover all packet fields, tags and metadata.
> Other than that it is ready for a formal patch integration in my opinion if there are no objections. Please advise.
Our mails crossed, I've just replied to the RFC :)
Yes we need to progress if we want to meet the deadline.
More reviews may help.
next prev parent reply other threads:[~2021-01-05 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 1:31 [dpdk-dev] [RFC] ethdev: introduce copy_field rte flow action Alexander Kozyrev
2021-01-05 22:12 ` Alexander Kozyrev
2021-01-05 22:18 ` Thomas Monjalon [this message]
2021-01-05 22:16 ` Thomas Monjalon
2021-01-07 14:17 ` Alexander Kozyrev
2021-01-07 15:06 ` Thomas Monjalon
2021-01-07 15:10 ` Alexander Kozyrev
2021-01-07 15:17 ` Thomas Monjalon
2021-01-07 15:22 ` Alexander Kozyrev
2021-01-07 16:54 ` Thomas Monjalon
2021-01-07 16:57 ` Alexander Kozyrev
2021-01-07 17:05 ` Thomas Monjalon
2021-01-07 20:14 ` Alexander Kozyrev
2021-01-07 20:21 ` Thomas Monjalon
2021-01-08 12:16 ` Slava Ovsiienko
2021-01-10 6:50 ` Ori Kam
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=9148098.Iffu9yAPz8@thomas \
--to=thomas@monjalon.net \
--cc=akozyrev@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=orika@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.