DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: olegpoly123 <olegp123@walla.co.il>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Oeg Polyakov <opolyakov@northforgeinc.com>
Subject: Re: [dpdk-dev] [PATCH] net/tap: fix missing _SC_IOV_MAX
Date: Thu, 7 Mar 2019 22:31:34 +0000	[thread overview]
Message-ID: <EEA36899-1231-4D2E-A13B-88EFD86D1FA6@intel.com> (raw)
In-Reply-To: <20190307222523.24620-1-olegp123@walla.co.il>



> On Mar 7, 2019, at 4:25 PM, olegpoly123 <olegp123@walla.co.il> wrote:
> 
> If the value _SC_IOV_MAX is missing, sysconf returns -1.
> In this case, iov_max is set to a default value of 1024.
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Oeg Polyakov <opolyakov@northforgeinc.com>
> ---
> drivers/net/tap/rte_eth_tap.c | 5 +++++
> 1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
> index 6f5109fca..cd48b2b2a 100644
> --- a/drivers/net/tap/rte_eth_tap.c
> +++ b/drivers/net/tap/rte_eth_tap.c
> @@ -1326,6 +1326,11 @@ tap_rx_queue_setup(struct rte_eth_dev *dev,
> 	struct rx_queue *rxq = &internals->rxq[rx_queue_id];
> 	struct rte_mbuf **tmp = &rxq->pool;
> 	long iov_max = sysconf(_SC_IOV_MAX);
> +	if (iov_max <= 0) {
> +		TAP_LOG(WARNING,
> +			"_SC_IOV_MAX is not defined. Using 1024 as default\n");
> +		iov_max = 1024;

Can I get you to create a define for the 1024 value e.g. #define TAP_IOV_DEFAULT_MAX 1024 or something of that type.
Also change the TAP_LOG to use the define. 
> +	}
> 	uint16_t nb_desc = RTE_MIN(nb_rx_desc, iov_max - 1);
> 	struct iovec (*iovecs)[nb_desc + 1];
> 	int data_off = RTE_PKTMBUF_HEADROOM;
> -- 
> 2.14.1
> 

Regards,
Keith

  reply	other threads:[~2019-03-07 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 22:25 olegpoly123
2019-03-07 22:31 ` Wiles, Keith [this message]
2019-03-08 18:00 olegpoly123
2019-03-08 18:06 ` Wiles, Keith
2019-03-08 18:54   ` Thomas Monjalon
2019-03-09  3:02 ` Stephen Hemminger

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=EEA36899-1231-4D2E-A13B-88EFD86D1FA6@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=olegp123@walla.co.il \
    --cc=opolyakov@northforgeinc.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).