DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Wei Dai <wei.dai@intel.com>, <thomas@monjalon.net>,
	<ferruh.yigit@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: fix comments for offload capabilities
Date: Wed, 9 May 2018 18:23:26 +0300	[thread overview]
Message-ID: <ddf46e88-ac44-d4bc-2198-8ffc8f3858d6@solarflare.com> (raw)
In-Reply-To: <1525869126-51223-1-git-send-email-wei.dai@intel.com>

On 05/09/2018 03:32 PM, Wei Dai wrote:
> Indeed, rx_offload_capa or tx_offload_capa  in struct rte_eth_dev_info
> includes not only per port offloading features but also per queue ones.
> This patch make its meaning much clearer.
>
> Fixes: ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
> Fixes: cba7f53b717d ("ethdev: introduce Tx queue offloads API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Wei Dai <wei.dai@intel.com>
>
> ---
> v2: fix coding style issues
> ---
>   lib/librte_ethdev/rte_ethdev.h | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
> index 7ccf4ba..98e3114 100644
> --- a/lib/librte_ethdev/rte_ethdev.h
> +++ b/lib/librte_ethdev/rte_ethdev.h
> @@ -1067,9 +1067,13 @@ struct rte_eth_dev_info {
>   	uint16_t max_vfs; /**< Maximum number of VFs. */
>   	uint16_t max_vmdq_pools; /**< Maximum number of VMDq pools. */
>   	uint64_t rx_offload_capa;
> -	/**< Device per port RX offload capabilities. */
> +	/**< Rx offload capabilities including all per port ones
> +	 * and all per queue ones.
> +	 */
>   	uint64_t tx_offload_capa;
> -	/**< Device per port TX offload capabilities. */
> +	/**< Tx offload capabilities including all per port ones
> +	 * and all per queue ones.
> +	 */
>   	uint64_t rx_queue_offload_capa;
>   	/**< Device per queue RX offload capabilities. */
>   	uint64_t tx_queue_offload_capa;

Just a minor nit.
May I suggest to put comments before structure member and use /**.
Right now it looks very confusing.

Andrew.

      reply	other threads:[~2018-05-09 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 11:21 [dpdk-dev] [PATCH] ethdev: fix comments for offload capabilites Wei Dai
2018-05-09 12:32 ` [dpdk-dev] [PATCH v2] ethdev: fix comments for offload capabilities Wei Dai
2018-05-09 15:23   ` Andrew Rybchenko [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=ddf46e88-ac44-d4bc-2198-8ffc8f3858d6@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=wei.dai@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).