From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <ramirose@gmail.com>, dev@dpdk.org
Cc: tiago.lam@intel.com
Subject: Re: [dpdk-dev] [dpdk-next-net] [PATCH] net/af_packet: fix docs guide
Date: Thu, 20 Dec 2018 18:54:45 +0000 [thread overview]
Message-ID: <c570a1f7-9674-9998-86d1-aeba20a5e7ce@intel.com> (raw)
In-Reply-To: <20181218071037.7762-1-ramirose@gmail.com>
On 12/18/2018 7:10 AM, Rami Rosen wrote:
> The framecnt option represents a counter (integer) that does not
> reflect size. It is somewhat parallel in this sense to the framecount
> member of pkt_rx_queue/pkt_tx_queue (or tp_frame_nr in tpacket_req).
> This patch removes the size indicator of bytes ("B") from framecnt in
> the af_packet guide.
>
> Fixes: c8dba1ee6cde ("doc: add af_packet PMD guide")
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
(Squashed into relevant commit in next-net, thanks.)
prev parent reply other threads:[~2018-12-20 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 7:10 Rami Rosen
2018-12-20 18:54 ` 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=c570a1f7-9674-9998-86d1-aeba20a5e7ce@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.com \
--cc=tiago.lam@intel.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).