From: Stephen Hemminger <stephen@networkplumber.org>
To: Ouyang Changchun <changchun.ouyang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/3] ether: Update field name and description for queue start
Date: Tue, 22 Jul 2014 10:43:21 -0700 [thread overview]
Message-ID: <20140722104321.6107c937@haswell> (raw)
In-Reply-To: <1406015252-27804-2-git-send-email-changchun.ouyang@intel.com>
On Tue, 22 Jul 2014 15:47:30 +0800
Ouyang Changchun <changchun.ouyang@intel.com> wrote:
> + /**< If rx_enable_queue is true, rte_eth_dev_rx_queue_start must be
> + invocated after rte_eth_dev_start's invocation to start RX for
> + one queue, and rte_eth_dev_rx_queue_start instead of
> + rte_eth_dev_start is responsible for allocating mbuf from
> + mempool and setup the DMA physical address. It is useful in
> + such scenario: buffer address is not available at the point of
> + rte_eth_dev_start's invocation but available later, e.g. in
> + VHOST zero copy case, the buffer address to be setup DMA
> + address is available only after one VM startup. */
Good documentation about semantics is really valuable as long as it
kept up to date. In this case, the comment stands out which is not
a good thing.
An explanation this long belongs in documentation not in code.
Alternatively, if it is this hard to explain maybe it isn't the right design :-)
next prev parent reply other threads:[~2014-07-22 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 7:47 [dpdk-dev] [PATCH 0/3] Rename field name for RX/TX queue start/stop Ouyang Changchun
2014-07-22 7:47 ` [dpdk-dev] [PATCH 1/3] ether: Update field name and description for queue start Ouyang Changchun
2014-07-22 17:43 ` Stephen Hemminger [this message]
2014-07-22 7:47 ` [dpdk-dev] [PATCH 2/3] ixgbe: Rename field name for queue start in ixgbe PMD Ouyang Changchun
2014-07-22 7:47 ` [dpdk-dev] [PATCH 3/3] vhost: Update reference in user space vhost sample Ouyang Changchun
2014-07-22 9:37 ` [dpdk-dev] [PATCH 0/3] Rename field name for RX/TX queue start/stop Thomas Monjalon
2014-07-22 9:52 ` Chen, Jing D
2014-07-23 1:07 ` Ouyang, Changchun
2014-07-28 4:34 ` Ouyang, Changchun
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=20140722104321.6107c937@haswell \
--to=stephen@networkplumber.org \
--cc=changchun.ouyang@intel.com \
--cc=dev@dpdk.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 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).