From: Alexander Kozyrev <akozyrev@nvidia.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"ivan.malov@oktetlabs.ru" <ivan.malov@oktetlabs.ru>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>,
"ferruh.yigit@xilinx.com" <ferruh.yigit@xilinx.com>,
"Awal, Mohammad Abdul" <mohammad.abdul.awal@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH v5 0/7] ethdev: separate metering and marking from policing
Date: Mon, 26 Sep 2022 18:48:16 +0000 [thread overview]
Message-ID: <DM5PR12MB24055A4D3900D04C3E35BA7CAF529@DM5PR12MB2405.namprd12.prod.outlook.com> (raw)
> Hi Alexander,
>
> Thanks very much for your pseudo-code detailing the updated meter & flow
> operation!
>
> Should we setup another call sometime next week to go through it? I still see
> a few fuzzy things where we need to level set.
>
> Regards,
> Cristian
Hi Christian, do you still have questions/concerns about the proposed changes?
Do we need another call to sort them out or you got the idea of the overall design?
next reply other threads:[~2022-09-26 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:48 Alexander Kozyrev [this message]
2022-09-27 11:57 ` Dumitrescu, Cristian
-- strict thread matches above, loose matches on Subject: below --
2022-09-21 2:11 [PATCH v4 " Alexander Kozyrev
2022-09-26 14:57 ` [PATCH v5 " Alexander Kozyrev
2022-09-27 11:56 ` Dumitrescu, Cristian
2022-09-28 6:45 ` Ori Kam
2022-09-28 16:38 ` Ajit Khaparde
2022-09-29 7:51 ` Andrew Rybchenko
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=DM5PR12MB24055A4D3900D04C3E35BA7CAF529@DM5PR12MB2405.namprd12.prod.outlook.com \
--to=akozyrev@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).