From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Saygin, Artur" <artur.saygin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: DPDK and custom memory
Date: Sat, 30 Aug 2014 15:03:54 +0200 [thread overview]
Message-ID: <1971750.bXvAyT2929@xps13> (raw)
In-Reply-To: <B1E02754DD4D4F4EAC7A14C1202CE62073E8E330-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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-30 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 18:40 DPDK and custom memory Saygin, Artur
[not found] ` <B1E02754DD4D4F4EAC7A14C1202CE62073E8E330-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-30 13:03 ` Thomas Monjalon [this message]
2014-08-31 8:27 ` Alex Markuze
[not found] ` <B1E02754DD4D4F4EAC7A14C1202CE62073E8E8C7@ORSMSX102.amr.corp.intel.com>
[not found] ` <B1E02754DD4D4F4EAC7A14C1202CE62073E8E8C7-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-09-03 10:03 ` Neil Horman
[not found] ` <20140903100349.GA24854-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-09-19 0:13 ` Saygin, Artur
[not found] ` <B1E02754DD4D4F4EAC7A14C1202CE62073E9CC82-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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=1971750.bXvAyT2929@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=artur.saygin-ral2JQCrhuEAvxtiuMwx3w@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.