From: Dan Aloni <dan-HWkDggknmVpWk0Htik3J/w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] eal/linux: allow to map BARs with MSI-X tables, around them
Date: Wed, 28 Jan 2015 16:06:27 +0200 [thread overview]
Message-ID: <20150128140627.GA25787@gmail.com> (raw)
In-Reply-To: <1421915771-10376-1-git-send-email-dan-HWkDggknmVpWk0Htik3J/w@public.gmane.org>
On Thu, Jan 22, 2015 at 10:36:11AM +0200, Dan Aloni wrote:
> While VFIO doesn't allow us to map complete BARs with MSI-X tables,
> it does allow us to map around them in PAGE_SIZE granularity. There
> might be adapters that provide their registers in the same BAR
> but on a different page. For example, Intel's NVME adapter, though
> not a network adapter, provides only one MMIO BAR that contains
> the MSI-X table.
>
> Signed-off-by: Dan Aloni <dan-HWkDggknmVpWk0Htik3J/w@public.gmane.org>
> CC: Anatoly Burakov <anatoly.burakov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Has anyone reviewed this yet?
I am asking because I am interested to know whether someone is aiming
to integrate storage controllers support into DPDK, and this patch
could be instrumental.
--
Dan Aloni
next prev parent reply other threads:[~2015-01-28 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 8:36 [PATCH] eal/linux: allow to map BARs with MSI-X tables, around them Dan Aloni
[not found] ` <1421915771-10376-1-git-send-email-dan-HWkDggknmVpWk0Htik3J/w@public.gmane.org>
2015-01-28 14:06 ` Dan Aloni [this message]
2015-01-28 15:01 ` Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E4512369780C3ECFA-kPTMFJFq+rHjxeytcECX8bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-28 22:04 ` Dan Aloni
2015-01-28 22:04 ` [PATCH v2] " Dan Aloni
[not found] ` <1422482693-14158-1-git-send-email-dan-HWkDggknmVpWk0Htik3J/w@public.gmane.org>
2015-01-29 10:22 ` Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E4512369780C3F021-kPTMFJFq+rHjxeytcECX8bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-01-29 10:25 ` Dan Aloni
2015-02-23 20:58 ` 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=20150128140627.GA25787@gmail.com \
--to=dan-hwkdggknmvpwk0htik3j/w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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.