From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/nfp: avoid access to sysfs resource0 file
Date: Wed, 27 Jun 2018 15:57:41 +0100 [thread overview]
Message-ID: <ca6cf402-6955-7d6e-e97a-af11fcb67859@intel.com> (raw)
In-Reply-To: <1530019761-27794-1-git-send-email-alejandro.lucero@netronome.com>
On 6/26/2018 2:29 PM, Alejandro Lucero wrote:
> NFP CPP interface dinamically configures NFP CPP BARs for accessing
> any NFP chip component from user space. This requires to map PCI BAR
> regions specifically. However, this does not require to do such map
> over the usual map done by VFIO or UIO drivers with the device PCI
> BARs.
>
> This patch avoids this remapping and therefore also avoids to access
> the device sysfs resource0 file for doing that remapping.
>
> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-06-27 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 13:29 Alejandro Lucero
2018-06-27 14:57 ` Ferruh Yigit [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=ca6cf402-6955-7d6e-e97a-af11fcb67859@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.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).