DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Nikhil Agarwal <nikhil.agarwal@linaro.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "david.hunt@intel.com" <david.hunt@intel.com>,
	"nikhil.agarwal@nxp.com" <nikhil.agarwal@nxp.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info
Date: Tue, 12 Dec 2017 10:45:42 +0000	[thread overview]
Message-ID: <HE1PR0502MB36593193193E704566C2FCE5D2340@HE1PR0502MB3659.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20171212100520.20502-1-nikhil.agarwal@linaro.org>

Hi Nikhil

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nikhil Agarwal
> Sent: Tuesday, December 12, 2017 12:05 PM
> To: dev@dpdk.org
> Cc: david.hunt@intel.com; nikhil.agarwal@nxp.com;
> hemant.agrawal@nxp.com; ferruh.yigit@intel.com
> Subject: [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info
> 
> Currently, if the  rte_eth_rx_burst() function returns a value less than
> *nb_pkts*, the application will assume that no more packets are present.
> 
> Some of the hw queue based hardware can only support smaller burst for RX
> and TX and thus break the expectation of the rx_burst API.
>

Doesn't such like devices PMDs should try to retrieve multiple HW burst to adjust the asked received  packet number?
 
> This patch adds support to provide the maximum burst size that can be
> supported by a given PMD. The dev_info is being memset to '0' in
> rte_ethdev library. The value of '0' indicates that any value for burst size can
> be supported i.e. no change for existing PMDs.
> 
> The application can now use the lowest available max_burst_size value for
> rte_eth_rx_burst.
> 

If you are talking about performance, maybe the right field to expose is something like "perf_burst_size" or "preferred_burst_size".
I also suggest to expose different fields for RX and for TX.
Maybe the rte_eth_rx\tx_burst() descriptions should be updated. 

Thanks
Matan.

> Signed-off-by: Nikhil Agarwal <nikhil.agarwal@linaro.org>
> ---
>  lib/librte_ether/rte_ethdev.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
> index 341c2d6..3ab6f02 100644
> --- a/lib/librte_ether/rte_ethdev.h
> +++ b/lib/librte_ether/rte_ethdev.h
> @@ -1047,6 +1047,7 @@ struct rte_eth_dev_info {
>  	/** Configured number of rx/tx queues */
>  	uint16_t nb_rx_queues; /**< Number of RX queues. */
>  	uint16_t nb_tx_queues; /**< Number of TX queues. */
> +	uint16_t max_burst_size; /**< MAX burst size, 0 for no limit. */
>  };
> 
>  /**
> --
> 2.7.4

  parent reply	other threads:[~2017-12-12 10:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 10:05 Nikhil Agarwal
2017-12-12 10:05 ` [dpdk-dev] [PATCH 2/3] net/dpaa: implement max burst size in dev info Nikhil Agarwal
2017-12-12 10:05 ` [dpdk-dev] [PATCH 3/3] examples/l3fwd-power: use device max burst size Nikhil Agarwal
2017-12-12 10:45 ` Matan Azrad [this message]
2017-12-12 11:03   ` [dpdk-dev] [PATCH 1/3] ethdev: add max burst size to device info Ananyev, Konstantin
2017-12-12 13:43     ` Shreyansh Jain
2017-12-13 12:52       ` Ananyev, Konstantin
2017-12-13 15:22         ` Shreyansh Jain
2018-05-22 22:17 ` Thomas Monjalon
2019-04-05 14:55   ` Ferruh Yigit
2019-04-05 14:55     ` Ferruh Yigit
2019-04-05 14:57     ` Yigit, Ferruh
2019-04-05 14:57       ` Yigit, Ferruh

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=HE1PR0502MB36593193193E704566C2FCE5D2340@HE1PR0502MB3659.eurprd05.prod.outlook.com \
    --to=matan@mellanox.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nikhil.agarwal@linaro.org \
    --cc=nikhil.agarwal@nxp.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).