patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: olegpoly123 <olegp123@walla.co.il>
Cc: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Oeg Polyakov <opolyakov@northforgeinc.com>
Subject: Re: [dpdk-stable] [PATCH v2 2/2] Define macro for iov_max default value
Date: Fri, 8 Mar 2019 16:33:13 +0000	[thread overview]
Message-ID: <E7E26758-7F02-4E31-A501-82E6D5B8F5F7@intel.com> (raw)
In-Reply-To: <20190308155547.1695-2-olegp123@walla.co.il>



> On Mar 8, 2019, at 9:55 AM, olegpoly123 <olegp123@walla.co.il> wrote:
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Oeg Polyakov <opolyakov@northforgeinc.com>
> ---
> drivers/net/tap/rte_eth_tap.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/tap/rte_eth_tap.c b/drivers/net/tap/rte_eth_tap.c
> index cd48b2b2a..e7da73509 100644
> --- a/drivers/net/tap/rte_eth_tap.c
> +++ b/drivers/net/tap/rte_eth_tap.c
> @@ -68,6 +68,8 @@
> /* IPC key for queue fds sync */
> #define TAP_MP_KEY "tap_mp_sync_queues"
> 
> +#define TAP_IOV_DEFAULT_MAX 1024
> +
> static int tap_devices_count;
> static struct rte_vdev_driver pmd_tap_drv;
> static struct rte_vdev_driver pmd_tun_drv;
> @@ -1328,8 +1330,8 @@ tap_rx_queue_setup(struct rte_eth_dev *dev,
> 	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;
> +			"_SC_IOV_MAX is not defined. Using %d as default\n", TAP_IOV_DEFAULT_MAX);
> +		iov_max = TAP_IOV_DEFAULT_MAX;

I am afraid your patch will not work on top of the current code in the master repo, it appears you created a patch on top of your v1 patch.
Maybe you should squash the first patch and this one, then it should be correct.
> 	}
> 	uint16_t nb_desc = RTE_MIN(nb_rx_desc, iov_max - 1);
> 	struct iovec (*iovecs)[nb_desc + 1];
> -- 
> 2.14.1
> 

Regards,
Keith

       reply	other threads:[~2019-03-08 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190308155547.1695-1-olegp123@walla.co.il>
     [not found] ` <20190308155547.1695-2-olegp123@walla.co.il>
2019-03-08 16:33   ` Wiles, Keith [this message]
2019-03-08 17:29 ` [dpdk-stable] [dpdk-dev] [PATCH v2 1/2] net/tap: fix missing _SC_IOV_MAX 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=E7E26758-7F02-4E31-A501-82E6D5B8F5F7@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).