From: Kristian Evensen <kristian.evensen@gmail.com>
To: netfilter@vger.kernel.org
Subject: Target in two chains simultaneously
Date: Tue, 10 Nov 2009 23:32:40 +0100 [thread overview]
Message-ID: <4AF9EA08.6090709@gmail.com> (raw)
Hello,
I am working on a small project where I need (or at least want) to base
outgoing TCP load balancing on incoming ACKs. My first idea was to write
a threaded kernel module using netfilter, but I am not sure if that is
needed. Also, since every outgoing/incoming packet has to go through
that module it might affect performance severly.
I am not too familiar with the iptables-architecture, but would it make
sense to use the same module in two chains (for example OUTPUT and
INPUT) simultaneously and then share data structures between them? How
will this perform, and would I need to do any syncronization between the
shared structures? For example, can the processing of an outgoing packet
be interrupted by an incoming?
Thanks in advance for any help,
Kristian
reply other threads:[~2009-11-10 22:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AF9EA08.6090709@gmail.com \
--to=kristian.evensen@gmail.com \
--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 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).