From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] PCI domain size
Date: Wed, 07 Jun 2017 16:23:09 +0200 [thread overview]
Message-ID: <4912406.Tfa8CUZAWC@xps> (raw)
In-Reply-To: <20170524164008.4d4e8e7b@xeon-e3>
25/05/2017 01:40, Stephen Hemminger:
> While working on SR-IOV support on Azure, it was discovered that some applications
> and drivers do not support full size PCI domains. On Azure environment the PCI pass
> through device has a synthetic domain value (ie generated by host) which is > 16 bits.
>
> The common PCI utilities (pci-utils) and Linux kernel both support
> full 32 bits but DPDK does not. FreeBSD also supports 32 bit domains.
>
> Changing the one place in DPDK (rte_pci.h) in source is trivial but of course
> it is a major ABI breakage which is a complete flag day. I.e no binary compatiabilty
> is possible.
I guess you are talking about
struct rte_pci_addr {
uint16_t domain;
uint8_t bus;
uint8_t devid;
uint8_t function;
};
I do not see why we would not change it to comply to the standard.
Do you want to propose a deprecation?
prev parent reply other threads:[~2017-06-07 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 23:40 Stephen Hemminger
2017-06-07 14:23 ` Thomas Monjalon [this message]
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=4912406.Tfa8CUZAWC@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).