From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Subject: Re: [PATCH v2] eventdev/eth_rx: update adapter create APIs
Date: Thu, 10 Aug 2023 18:55:34 +0530 [thread overview]
Message-ID: <CALBAE1P6_ziuFAxgcPR9dDUrQFLBwi3iHgZSD_C4TsovRQbuQg@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB3868EABB792EA1D6D589FF3DA113A@DM6PR11MB3868.namprd11.prod.outlook.com>
On Thu, Aug 10, 2023 at 5:28 PM Naga Harish K, S V
<s.v.naga.harish.k@intel.com> wrote:
>
> Hi Jerin,
> Thinking of another approach for this patch.
> Instead of changing all create APIs, update rte_event_eth_rx_adapter_create_ext() alone with additional parameters.
> rte_event_eth_rx_adapter_create() and rte_event_eth_rx_adapter_create_with_params() APIs will be untouched.
I am not sure if that is for any help to existing application which is
using rte_event_eth_rx_adapter_create_ext() and
it needs to support two DPDK versions.
Also, rte_event_eth_rx_adapter_create_ext() is not experimental API,
we need depreciation notice to change API.
prev parent reply other threads:[~2023-08-10 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:40 [RFC] " Naga Harish K S V
2023-08-01 10:28 ` Jerin Jacob
2023-08-01 13:51 ` [PATCH v2] " Naga Harish K S V
2023-08-01 15:23 ` Jerin Jacob
2023-08-02 14:19 ` Naga Harish K, S V
2023-08-02 16:12 ` Jerin Jacob
2023-08-10 7:38 ` Naga Harish K, S V
2023-08-10 8:07 ` Jerin Jacob
2023-08-10 11:58 ` Naga Harish K, S V
2023-08-10 13:25 ` Jerin Jacob [this message]
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=CALBAE1P6_ziuFAxgcPR9dDUrQFLBwi3iHgZSD_C4TsovRQbuQg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=s.v.naga.harish.k@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).