From: Alex Markuze <alex@weka.io>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Saygin, Artur" <artur.saygin@intel.com>
Subject: Re: [dpdk-dev] DPDK and custom memory
Date: Sun, 31 Aug 2014 11:27:05 +0300 [thread overview]
Message-ID: <CAKfHP0W0qbxvFbV=GesWwDEmOvQ2bJ83CzUcPJB42L8a6depOg@mail.gmail.com> (raw)
In-Reply-To: <1971750.bXvAyT2929@xps13>
Artur, I don't have the details of what you are trying to achieve, but
it sounds like something that is covered by IOMMU, SW or HW. The
IOMMU creates an iova (I/O Virtual address) the nic can access the
range is controlled with flags passed to the dma_map functions.
So I understand your question this way, How does the DPDK work with
IOMMU enabled system and can you influence the mapping?
On Sat, Aug 30, 2014 at 4:03 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> Hello,
>
> 2014-08-29 18:40, Saygin, Artur:
>> Imagine a PMD for an FPGA-based NIC that is limited to accessing certain
>> memory regions <system, PCI, etc>.
>
> Does it mean Intel is making an FPGA-based NIC?
>
>> Is there a way to make DPDK use that exact memory?
>
> Maybe I don't understand the question well, because it doesn't seem really
> different of what other PMDs do.
> Assuming your NIC is PCI, you can access it via uio (igb_uio) or VFIO.
>
>> Perhaps this is more of a hugetlbfs question than DPDK but I thought I'd
>> start here.
>
> It's a pleasure to receive new drivers.
> Welcome here :)
>
> --
> Thomas
next prev parent reply other threads:[~2014-08-31 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B1E02754DD4D4F4EAC7A14C1202CE62073E8E330@ORSMSX102.amr.corp.intel.com>
2014-08-30 13:03 ` Thomas Monjalon
2014-08-31 8:27 ` Alex Markuze [this message]
[not found] ` <B1E02754DD4D4F4EAC7A14C1202CE62073E8E8C7@ORSMSX102.amr.corp.intel.com>
2014-09-03 10:03 ` Neil Horman
2014-09-19 0:13 ` Saygin, Artur
2014-09-19 10:18 ` Neil Horman
2014-09-02 13:47 ` Neil Horman
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='CAKfHP0W0qbxvFbV=GesWwDEmOvQ2bJ83CzUcPJB42L8a6depOg@mail.gmail.com' \
--to=alex@weka.io \
--cc=artur.saygin@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).