DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Subject: Re: RFC: adapter instance get api proposal
Date: Sat, 4 Jun 2022 15:05:54 +0530	[thread overview]
Message-ID: <CALBAE1NpHVySreEkG4+Z55UJtDNBsfHBa-BMyAKgZN60LEzjrw@mail.gmail.com> (raw)
In-Reply-To: <MW4PR11MB5911BEECAD60217A0A8473F587A19@MW4PR11MB5911.namprd11.prod.outlook.com>

On Fri, Jun 3, 2022 at 9:47 PM Kundapura, Ganapati
<ganapati.kundapura@intel.com> wrote:
>
> Hi dpdk-dev,
>
>    I would like to submit adapter instance get api to retrieve the Rx/Tx adapter instance id for for a Rx/Tx queue
>
>
>
> int
>
> rte_event_eth_rx_adapter_queue_instance_get(uint16_t eth_dev_id,
>
>                                             uint16_t rx_queue_id, uint8_t *instance_id)
>
>
>
> and
>
>
>
> int
>
> rte_event_eth_tx_adapter_queue_instance_get(uint16_t eth_dev_id,
>
>                                             uint16_t tx_queue_id, uint8_t *instance_id)
>
>
>
> When application creates multiple adapter instances and adds queues to different adapter instances,
>
> It’s difficult to maintain which queue belongs to which adapter instance.
>
>
>
> With this api, application need not manage the instance id’s for the queues.  It can query the
>
> Instance id for the specified queue.
>
>
>
> I look forward feedback on this proposal to submit patch for the review.


I hope it will be a common code that all PMD can use.
You may reduce the length of function as rte_event_eth_tx_adapter_instance_get()
IMO, Rest looks good


>
>
>
> Thanks,
>
> Ganapati

      reply	other threads:[~2022-06-04  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 16:17 Kundapura, Ganapati
2022-06-04  9:35 ` 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=CALBAE1NpHVySreEkG4+Z55UJtDNBsfHBa-BMyAKgZN60LEzjrw@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=ganapati.kundapura@intel.com \
    --cc=jay.jayatheerthan@intel.com \
    --cc=jerinj@marvell.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).