From: Ferruh Yigit <ferruh.yigit@intel.com>
To: olegpoly123 <olegp123@walla.co.il>,
keith.wiles@intel.com, thomas@monjalon.net
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v7] net/tap: fix missing _SC_IOV_MAX
Date: Thu, 21 Mar 2019 17:40:59 +0000 [thread overview]
Message-ID: <cc9370c5-ed51-d0cc-1710-f2d3a423087b@intel.com> (raw)
In-Reply-To: <20190318182047.5210-1-olegp123@walla.co.il>
On 3/18/2019 6:20 PM, olegpoly123 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.
> This should never happen except for redhat bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1504165
>
> Fixes: ec12df9504fe ("net/tap: fix support for large Rx queues")
> Cc: stable@dpdk.org
>
> Signed-off-by: Oleg Polyakov <olegp123@walla.co.il>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-03-21 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 18:20 olegpoly123
2019-03-21 17:40 ` Ferruh Yigit [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=cc9370c5-ed51-d0cc-1710-f2d3a423087b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--cc=olegp123@walla.co.il \
--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).