DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2 0/3] 32 bit PCI domain support
Date: Thu, 22 Jun 2017 08:56:38 -0700	[thread overview]
Message-ID: <20170622155641.25916-1-stephen@networkplumber.org> (raw)

The PCI address consists of  domain, bus, device, function.
The domain value is limited to 16 bits when received from ACPI,
but on virtual environments the host may use the full 32 bits to
distinguish direct hardware from synthetic buses.

Stephen Hemminger (3):
  pci: remove unnecessary casts from strtoul
  eal: PCI domain should be 32 bits
  mlx5: handle 32 bit PCI domain

 drivers/net/mlx5/mlx5_ethdev.c          |  2 +-
 lib/librte_eal/common/include/rte_pci.h | 12 ++++++------
 lib/librte_eal/linuxapp/eal/eal_pci.c   |  8 ++++----
 3 files changed, 11 insertions(+), 11 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-06-22 15:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 15:56 Stephen Hemminger [this message]
2017-06-22 15:56 ` [dpdk-dev] [PATCH v2 1/3] pci: remove unnecessary casts from strtoul Stephen Hemminger
2017-06-22 15:56 ` [dpdk-dev] [PATCH v2 2/3] eal: PCI domain should be 32 bits Stephen Hemminger
2017-06-22 16:05   ` Thomas Monjalon
2017-06-22 16:23     ` Stephen Hemminger
2017-06-22 15:56 ` [dpdk-dev] [PATCH v2 3/3] mlx5: handle 32 bit PCI domain Stephen Hemminger
2017-06-22 16:17   ` Thomas Monjalon
2017-06-22 16:41     ` Stephen Hemminger
2017-06-22 16:42     ` Stephen Hemminger
2017-06-22 17:04       ` 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=20170622155641.25916-1-stephen@networkplumber.org \
    --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 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).