From: Shivani Bhardwaj <shivanib134@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nft] src: evaluate: Show error for fanout without balance
Date: Thu, 7 Apr 2016 22:48:13 +0530 [thread overview]
Message-ID: <CAKHNQQEiswUESDHaTAroCYRCwjPJDGD=9NzhWhJ4Uh=g0nLh-A@mail.gmail.com> (raw)
In-Reply-To: <20160407171317.GA6225@salvia>
On Thu, Apr 7, 2016 at 10:43 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Thu, Apr 07, 2016 at 03:06:40PM +0530, Shivani Bhardwaj wrote:
>> The idea of fanout option is to improve the performance by indexing CPU
>> ID to map packets to the queues. This is used for load balancing.
>> Fanout option is not required when there is a single queue specified.
>>
>> According to iptables, queue balance should be specified in order to use
>> fanout, following that, throw an error in nftables if the range of
>> queues for load balancing is not specified with the fanout option.
>
> Curious, how does iptables behave when you pass fanout and a single
> queue?
>
It throws an error:
$ sudo iptables -A FORWARD -j NFQUEUE --queue-num 0 --queue-cpu-fanout
iptables v1.6.0: NFQUEUE: option "--queue-cpu-fanout" also requires
"--queue-balance".
Try `iptables -h' or 'iptables --help' for more information.
Since, queue-balance is done as queue num with a range in nftables, I
thought it should follow the same routine as iptables.
> Could you also include how the nft error output looks like after your
> patch in your description?
>
Yes I'll do that.
Thanks.
> Thanks.
prev parent reply other threads:[~2016-04-07 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 9:36 [PATCH nft] src: evaluate: Show error for fanout without balance Shivani Bhardwaj
2016-04-07 17:13 ` Pablo Neira Ayuso
2016-04-07 17:18 ` Shivani Bhardwaj [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='CAKHNQQEiswUESDHaTAroCYRCwjPJDGD=9NzhWhJ4Uh=g0nLh-A@mail.gmail.com' \
--to=shivanib134@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).