From: David Marchand <david.marchand@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/2] eal: mmap uio resources using resourceX files
Date: Tue, 24 Feb 2015 13:39:46 +0100 [thread overview]
Message-ID: <CALwxeUuGcuOfKKhXb7Xb5ALWydatcGHYrZ5sPMOPnJeAyz+dTA@mail.gmail.com> (raw)
In-Reply-To: <1424780404-30824-2-git-send-email-bruce.richardson@intel.com>
On Tue, Feb 24, 2015 at 1:20 PM, Bruce Richardson <
bruce.richardson@intel.com> wrote:
> Instead of distinguishing the BAR mappings via offset within a single
> file, originally /dev/uioX, switch to mapping each individual bar via
> the appropriately numbered resourceX file.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> lib/librte_eal/common/include/rte_pci.h | 2 +-
> lib/librte_eal/linuxapp/eal/eal_pci_init.h | 1 +
> lib/librte_eal/linuxapp/eal/eal_pci_uio.c | 34
> ++++++++++++++++--------------
> lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 1 +
> 4 files changed, 21 insertions(+), 17 deletions(-)
>
As long as igb_uio / uio_pci_generic both work, this is fine for me.
ack.
--
David Marchand
next prev parent reply other threads:[~2015-02-24 12:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 5:30 [dpdk-dev] Testpmd returns error Tetsuya Mukawa
2015-02-22 14:17 ` Thomas Monjalon
2015-02-22 16:19 ` David Marchand
2015-02-22 18:51 ` Richardson, Bruce
2015-02-22 20:31 ` Bruce Richardson
2015-02-22 20:46 ` Bruce Richardson
2015-02-23 2:33 ` Tetsuya Mukawa
2015-02-23 11:12 ` Bruce Richardson
2015-02-23 11:36 ` Tetsuya Mukawa
2015-02-23 14:57 ` [dpdk-dev] [PATCH] eal: mmap uio resources using resourceX files Bruce Richardson
2015-02-23 15:00 ` Bruce Richardson
2015-02-23 15:30 ` Iremonger, Bernard
2015-02-24 9:21 ` Tetsuya Mukawa
2015-02-23 17:02 ` [dpdk-dev] [PATCH v2 0/2] fix and improve uio_pci_generic support Bruce Richardson
2015-02-23 17:02 ` [dpdk-dev] [PATCH v2 1/2] eal: mmap uio resources using resourceX files Bruce Richardson
2015-02-23 17:02 ` [dpdk-dev] [PATCH v2 2/2] eal: populate uio_maps from pci mem_resources array Bruce Richardson
2015-02-24 10:53 ` [dpdk-dev] [PATCH v2 0/2] fix and improve uio_pci_generic support Bruce Richardson
2015-02-24 11:23 ` David Marchand
2015-02-24 11:32 ` Bruce Richardson
2015-02-24 12:35 ` David Marchand
2015-02-24 12:20 ` [dpdk-dev] [PATCH v3 " Bruce Richardson
2015-02-24 12:20 ` [dpdk-dev] [PATCH v3 1/2] eal: mmap uio resources using resourceX files Bruce Richardson
2015-02-24 12:39 ` David Marchand [this message]
2015-02-24 12:20 ` [dpdk-dev] [PATCH v3 2/2] eal: populate uio_maps from pci mem_resources array Bruce Richardson
2015-02-24 12:38 ` David Marchand
2015-02-24 13:30 ` [dpdk-dev] [PATCH v4 0/3] fix and improve uio_pci_generic support Bruce Richardson
2015-02-24 13:30 ` [dpdk-dev] [PATCH v4 1/3] eal: mmap uio resources using resourceX files Bruce Richardson
2015-02-24 13:30 ` [dpdk-dev] [PATCH v4 2/3] eal: populate uio_maps from pci mem_resources array Bruce Richardson
2015-02-24 13:30 ` [dpdk-dev] [PATCH v4 3/3] eal: remove unnecessary check for primary instance Bruce Richardson
2015-02-24 21:33 ` [dpdk-dev] [PATCH v4 0/3] fix and improve uio_pci_generic support 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=CALwxeUuGcuOfKKhXb7Xb5ALWydatcGHYrZ5sPMOPnJeAyz+dTA@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=bruce.richardson@intel.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).