DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jay Rolette <rolette@infiniteio.com>
To: Dev <dev@dpdk.org>
Subject: [dpdk-dev] Any way to control port_id mapping?
Date: Tue, 27 Jan 2015 20:26:53 -0600	[thread overview]
Message-ID: <CADNuJVo2mmRRwh47QdkddfGAj8ZNKsn5EEu-ovC3XEG0B_DRmw@mail.gmail.com> (raw)

Is there a way to control what ethernet port gets mapped to each port_id in
DPDK?

>From what I've seen, it looks like the port_id values just get assigned
based on the order they come back in the PCI probe/scan. Ideally, I'd like
to have the port_id values map reasonably directly to the customer-facing
labels on my appliance.

Label  : port_id
------   -------
Port 1 : 0
Port 2 : 1
Port 3 : 2
etc.

The PCI bus:slot.function values of the ethernet ports doesn't just sort
cleanly (no surprise).

I can work around it at higher levels, but it is a lot easier for debugging
and stats if there is a way to control how DPDK maps physical ports to
port_id values.

I didn't see anything in the docs or example apps so presumably the answer
is no, but thought I'd ask just in case.

Is that something other folks would find useful?

Thanks,
Jay

                 reply	other threads:[~2015-01-28  2:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CADNuJVo2mmRRwh47QdkddfGAj8ZNKsn5EEu-ovC3XEG0B_DRmw@mail.gmail.com \
    --to=rolette@infiniteio.com \
    --cc=dev@dpdk.org \
    /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).