All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gaetan Rivet <grive@u256.net>
Cc: dev@dpdk.org, Chas Williams <chas3@att.com>,
	Liron Himi <lironh@marvell.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v1] ethdev: add rte_device to port_id function
Date: Fri, 17 Apr 2020 13:44:35 -0700	[thread overview]
Message-ID: <20200417134435.53da1af8@hermes.lan> (raw)
In-Reply-To: <a62bdf6dad57737ffc169e1d2d6717efdec9436d.1587142035.git.grive@u256.net>

On Fri, 17 Apr 2020 18:48:37 +0200
Gaetan Rivet <grive@u256.net> wrote:

> +/**
> + * Find the owned ethdev port id of an `rte_device`.
> + *
> + * @param dev
> + *   An `rte_device`.
> + * @param owner
> + *   An owner id. Use `RTE_ETH_DEV_NO_OWNER` for ownerless ports.
> + *
> + * @return
> + *   The port id of an `rte_device` if it is owned by `owner`.
> + *   `RTE_MAX_ETHPORTS` otherwise.
> + */
> +__rte_experimental
> +uint16_t rte_eth_port_from_dev_owned_by(const struct rte_device *dev,
> +					const uint64_t owner);
> +

Ok, but why introduce API with no users?
Also a device could in theory be owned multiple times by the same owner.
For example if two NIC's from same vendor were used in bonding.

  reply	other threads:[~2020-04-17 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 16:48 [dpdk-dev] [PATCH v1] ethdev: add rte_device to port_id function Gaetan Rivet
2020-04-17 20:44 ` Stephen Hemminger [this message]
2020-04-19 19:36   ` Gaëtan Rivet

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=20200417134435.53da1af8@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=arybchenko@solarflare.com \
    --cc=chas3@att.com \
    --cc=dev@dpdk.org \
    --cc=grive@u256.net \
    --cc=lironh@marvell.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 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.