From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: PCI domain size
Date: Wed, 24 May 2017 16:40:08 -0700 [thread overview]
Message-ID: <20170524164008.4d4e8e7b@xeon-e3> (raw)
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.
next reply other threads:[~2017-05-24 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 23:40 Stephen Hemminger [this message]
2017-06-07 14:23 ` PCI domain size 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=20170524164008.4d4e8e7b@xeon-e3 \
--to=stephen@networkplumber.org \
--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 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.