From: Stephen Hemminger <stephen@networkplumber.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: support PCI domains
Date: Fri, 22 Jul 2016 14:12:59 -0700 [thread overview]
Message-ID: <20160722141259.35ea0a7e@xeon-e3> (raw)
In-Reply-To: <1469201650-32447-1-git-send-email-okaya@codeaurora.org>
On Fri, 22 Jul 2016 11:34:10 -0400
Sinan Kaya <okaya@codeaurora.org> wrote:
> The current code is enumerating devices based on bus, device and function
> pairs. This does not work well for architectures with multiple PCI
> segments/domains. Multiple PCI devices will have the same BDF value but
> different segment numbers (01:01:01.0 and 02:01:01.0) for instance.
>
> Adding segment numbers to device naming so that we can uniquely identify
> devices.
>
> Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
I ran into this yes. There is a small risk of breaking some application that
assumed something about names though.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2016-07-22 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 15:34 Sinan Kaya
2016-07-22 21:12 ` Stephen Hemminger [this message]
2016-07-22 22:56 ` Sinan Kaya
2016-10-04 8:15 ` Thomas Monjalon
2016-10-04 13:59 ` Sinan Kaya
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=20160722141259.35ea0a7e@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=okaya@codeaurora.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).