From: "Doherty, Declan" <declan.doherty@intel.com>
To: Anoob Joseph <anoobj@marvell.com>,
"Shetty, Praveen" <praveen.shetty@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] examples/ipsec-secgw: load/unload esp-ah DDP file
Date: Wed, 11 Mar 2020 13:35:56 +0000 [thread overview]
Message-ID: <4f4859c0-ca04-fc0c-db9b-934727f4a2bd@intel.com> (raw)
In-Reply-To: <MN2PR18MB2877290D408317E63A1A4415DFFF0@MN2PR18MB2877.namprd18.prod.outlook.com>
On 10/03/2020 4:24 PM, Anoob Joseph wrote:
> Hi Praveen,
>
> [Anoob] Rather than calling PMD specific functions from all applications, it might be better to introduce the same via 'devargs' to the PMD.
>
> [Praveen Shetty] We will investigate further on this.
>
> Probably let's converge on this before sending v2. I don't think we should add a new option just specific to one PMD. Devargs already provides the required framework and other PMDs are already using it.
I agree this would be better handled by driver specific devargs
>
> @Konstatin, @Akhil,
> What is your take on this?
>
> Thanks,
> Anoob
>
>> -----Original Message-----
>> From: Shetty, Praveen <praveen.shetty@intel.com>
>> Sent: Tuesday, March 10, 2020 5:11 PM
>> To: Anoob Joseph <anoobj@marvell.com>; dev@dpdk.org; Doherty, Declan
>> <declan.doherty@intel.com>; Iremonger, Bernard
>> <bernard.iremonger@intel.com>; Ananyev, Konstantin
>> <konstantin.ananyev@intel.com>
>> Subject: [EXT] RE: [dpdk-dev] [PATCH v1] examples/ipsec-secgw: load/unload
>> esp-ah DDP file
>>
...
>>> --
>>> 2.17.1
>
next prev parent reply other threads:[~2020-03-11 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 5:56 Praveen Shetty
2020-03-06 9:59 ` Anoob Joseph
2020-03-10 11:41 ` Shetty, Praveen
2020-03-10 16:24 ` Anoob Joseph
2020-03-11 13:35 ` Doherty, Declan [this message]
2020-03-11 15:03 ` Ananyev, Konstantin
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=4f4859c0-ca04-fc0c-db9b-934727f4a2bd@intel.com \
--to=declan.doherty@intel.com \
--cc=anoobj@marvell.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=praveen.shetty@intel.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).