From: Patrick McHardy <kaber@trash.net>
To: "Mattias Rönnblom" <hofors@lysator.liu.se>
Cc: netfilter@vger.kernel.org
Subject: Re: Multiple nf_bind_pf to the same protocol
Date: Tue, 03 Nov 2009 11:50:29 +0100 [thread overview]
Message-ID: <4AF00AF5.9070205@trash.net> (raw)
In-Reply-To: <87639rhq7t.fsf@isengard.friendlyfire.se>
Mattias Rönnblom wrote:
> Patrick McHardy <kaber@trash.net> writes:
>
>> Mattias Rönnblom wrote:
>>> Hi,
>>>
>>> with NFQUEUE and the libnetfilter_queue library, is it possible to
>>> bind several applications to same protocol (for example, AF_INET)?
>>>
>>> That would be useful if you want to do load balancing on a multicore
>>> system, with a thread/process serving each NFQUEUE queue.
>>>
>>> After having a brief look at the NFQUEUE/libnetfilter_queue code, it
>>> looks like there's only single netlink fd for all queues, and the
>>> library does the demultiplexing. Would that mean I have to have a
>>> "front-end" thread distributing different servering threads?
>> You can bind them to different group numbers for the same AF.
>> The latest version of the NFQUEUE target even supports automatic
>> balancing between those groups based on a simple flow hash.
>
> Do you by "group number" mean NFQUEUE queue number? If so, how would I
> do that?
Yes. You can specify the netlink group number in the nfq_create_queue()
call.
> The data comes on a single netlink fd, which is serviced by
> one thread, which is suppose to give the data chunk to
> libnetfilter_queue (nfq_handle_packet). The libary executes a callback
> (depending on queue number) in the context of that thread. At least
> that is my understanding of NFQUEUE/libnetfilter_queue.
You can start multiple processes and bind each one to a seperate queue.
Alternatively you can create multiple queue handles in a multithreaded
programm.
prev parent reply other threads:[~2009-11-03 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 15:09 Multiple nf_bind_pf to the same protocol Mattias Rönnblom
2009-11-02 15:30 ` Patrick McHardy
2009-11-03 10:12 ` Mattias Rönnblom
2009-11-03 10:50 ` Patrick McHardy [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=4AF00AF5.9070205@trash.net \
--to=kaber@trash.net \
--cc=hofors@lysator.liu.se \
--cc=netfilter@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.