All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Ciara Loftus <ciara.loftus@intel.com>, dev@dpdk.org
Subject: Re: [PATCH] net/vhost: Add function to retreive the 'vid' for a given port id
Date: Wed, 14 Sep 2016 12:43:29 +0800	[thread overview]
Message-ID: <20160914044329.GX23158@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <28342659.xFrdpVFeBf@xps13>

On Tue, Sep 13, 2016 at 05:10:09PM +0200, Thomas Monjalon wrote:
> 2016-09-13 14:47, Ciara Loftus:
> > In some cases when using the vHost PMD, certain vHost library functions
> > may still need to be accessed. One such example is the
> > rte_vhost_get_queue_num function which returns the number of virtqueues
> > reported by the guest - information which is not exposed by the PMD.
> > 
> > This commit introduces a new rte_eth_vhost function that returns the
> > 'vid' associated with a given port id. This allows the PMD user to call
> > vHost library functions which require the 'vid' value.
> 
> I think we should not add any API to the PMDs.

In general, I agree with you.

> Maybe you are looking for a generic API in ethdev.

But maybe it's a bit hard to define a "right" generic API here. For this
case, the generic API I can think of could be:

- an API to get queue num, like rte_eth_get_queue_enabled_num
  I barely know NIC pmd drivers, but I doubt it's useful/meaningful for them.

- an API to get a PMD driver private (or specific) data.
  For vhost-pmd, it's vid. Again, I don't know what it could be for other nic
  drivers.

  This one may be a better option here, because it expose a key field to
  the application, vid, with which the application can invoke more vhost
  APIs. And apparently, it's not feasible to try to define a generic API
  for some (if not each) vhost APIs.
  

Or, better ideas?

	--yliu

  reply	other threads:[~2016-09-14  4:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 13:47 [PATCH] net/vhost: Add function to retreive the 'vid' for a given port id Ciara Loftus
2016-09-13 15:10 ` Thomas Monjalon
2016-09-14  4:43   ` Yuanhan Liu [this message]
2016-09-14  7:10     ` Thomas Monjalon
2016-09-14  7:21       ` Yuanhan Liu
2016-09-14  8:35         ` Thomas Monjalon
2016-09-18  8:27           ` Yuanhan Liu
2016-09-21 13:07             ` Thomas Monjalon
2016-09-22  2:36               ` Yuanhan Liu
2016-09-22 16:43                 ` Thomas Monjalon
2016-09-23  4:26                   ` Yuanhan Liu
2016-09-23  8:43                     ` Thomas Monjalon
2016-09-23  9:16                       ` Yuanhan Liu
2016-09-23  9:26                         ` Loftus, Ciara
2016-09-23 21:23                     ` Wiles, Keith
2016-09-26  3:19                       ` Yuanhan Liu
2016-09-26 13:12                       ` Thomas Monjalon
2016-09-26 13:18                         ` Bruce Richardson
2016-09-26 14:26                           ` Thomas Monjalon
2016-09-26 14:34                             ` Bruce Richardson
2016-09-26 16:24                               ` Iremonger, Bernard
2016-09-26 16:55                                 ` Thomas Monjalon
2016-09-26 17:05                                 ` Wiles, Keith
2016-09-28 16:59   ` Mcnamara, John
2016-09-29  9:21 ` Mcnamara, John
2016-09-29  9:30   ` Thomas Monjalon
2016-09-29 12:08   ` Yuanhan Liu

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=20160914044329.GX23158@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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.