From: Stephen Hemminger <stephen@networkplumber.org>
To: Mats Liljegren <liljegren.mats2@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] Introduce if_index field to struct rte_eth_dev_info
Date: Wed, 8 Jan 2014 22:30:12 -0800 [thread overview]
Message-ID: <CAOaVG15nLWGmhbXW7cW7sDxxRE9zRzGoim1GL0-cA642M0QYfg@mail.gmail.com> (raw)
In-Reply-To: <CA+xJJ19BFjhtdu9eOQuNbi0fexRWGUOVD4-yAEx9gPvbLbswKQ@mail.gmail.com>
Technically in Linux ifindex is unsigned 32 bit value. And 0 is
reserved as a marker.
Therefore why not use that semantic.
On Wed, Jan 8, 2014 at 1:46 AM, Mats Liljegren
<liljegren.mats2@gmail.com> wrote:
> This field is intended for pcap to describe the name of the interface
> as known to Linux. It is an interface index, but can be translated into
> an interface name using if_indextoname() function.
>
> When using pcap, interrupt affinity becomes important, and this field
> gives the application a chance to ensure that interrupt affinity is set
> to the lcore handling the device.
>
> Signed-off-by: Mats Liljegren <mats.liljegren@enea.com>
> ---
> lib/librte_ether/rte_ethdev.c | 1 +
> lib/librte_ether/rte_ethdev.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c
> index 859ec92..38c1ea1 100644
> --- a/lib/librte_ether/rte_ethdev.c
> +++ b/lib/librte_ether/rte_ethdev.c
> @@ -1037,6 +1037,7 @@ rte_eth_dev_info_get(uint8_t port_id, struct
> rte_eth_dev_info *dev_info)
> /* Default device offload capabilities to zero */
> dev_info->rx_offload_capa = 0;
> dev_info->tx_offload_capa = 0;
> + dev_info->if_index = -1;
> FUNC_PTR_OR_RET(*dev->dev_ops->dev_infos_get);
> (*dev->dev_ops->dev_infos_get)(dev, dev_info);
> dev_info->pci_dev = dev->pci_dev;
> diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
> index 302d378..5b80e5d 100644
> --- a/lib/librte_ether/rte_ethdev.h
> +++ b/lib/librte_ether/rte_ethdev.h
> @@ -787,6 +787,7 @@ struct rte_eth_conf {
> struct rte_eth_dev_info {
> struct rte_pci_device *pci_dev; /**< Device PCI information. */
> const char *driver_name; /**< Device Driver name. */
> + int if_index; /**< Index to bounded host interface, or -1 if
> none. Use if_indextoname() to translate into an interface name. */
> uint32_t min_rx_bufsize; /**< Minimum size of RX buffer. */
> uint32_t max_rx_pktlen; /**< Maximum configurable length of RX pkt. */
> uint16_t max_rx_queues; /**< Maximum number of RX queues. */
> --
> 1.8.3.2
next prev parent reply other threads:[~2014-01-09 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 9:46 Mats Liljegren
2014-01-09 6:30 ` Stephen Hemminger [this message]
2014-01-09 8:44 ` Mats Liljegren
2014-01-09 9:01 ` Thomas Monjalon
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=CAOaVG15nLWGmhbXW7cW7sDxxRE9zRzGoim1GL0-cA642M0QYfg@mail.gmail.com \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=liljegren.mats2@gmail.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).