From: "Lam, Tiago" <tiago.lam@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Cc: linville@tuxdriver.com
Subject: Re: [dpdk-dev] [PATCH] net/af_packet: add docs guide
Date: Tue, 18 Dec 2018 08:23:36 +0000 [thread overview]
Message-ID: <b261ee2d-e9a4-01d8-6f96-1dea3bba0acb@intel.com> (raw)
In-Reply-To: <87dbb7e9-eebb-7499-9959-4586990a7385@intel.com>
On 18/12/2018 00:39, Ferruh Yigit wrote:
> On 12/18/2018 12:31 AM, Ferruh Yigit wrote:
>> On 12/17/2018 9:14 AM, Tiago Lam wrote:
>>> As of commit 364e08f2bbc0, DPDK allows an aplication to send and receive
>>> raw packets using an AF_PACKET and PACKET_MMAP, when using a Linux
>>> Kernel. This complements it by adding a simple guide with the following
>>> information:
>>> - An introduction, where a brief explanation of this driver is given,
>>> pointing out the dependency on PACKET_MMAP;
>>> - Which options are supported at configuration time, while setting up an
>>> interface, and it's inherent limitations;
>>> - What the prerequisites are;
>>> - A command line example of how to set up a DPDK port using the
>>> af_packet driver.
>>>
>>> Since there's a dependency in PACKET_MMAP, the guide also points to the
>>> original Kernel documentation, so the reader can get more details.
>>>
>>> Signed-off-by: Tiago Lam <tiago.lam@intel.com>
> <...>
>>
>> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Applied to dpdk-next-net/master, thanks.
>
> (mentioned changes applied while merging, please confirm)
>
Thanks, Ferruh, for applying with the fixes.
I've re-build the docs and looks from here.
Tiago.
prev parent reply other threads:[~2018-12-18 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 9:14 Tiago Lam
2018-12-18 0:31 ` Ferruh Yigit
2018-12-18 0:39 ` Ferruh Yigit
2018-12-18 8:23 ` Lam, Tiago [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=b261ee2d-e9a4-01d8-6f96-1dea3bba0acb@intel.com \
--to=tiago.lam@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linville@tuxdriver.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).