From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] netfilter: arptables: use percpu jumpstack
Date: Thu, 2 Jul 2015 22:00:24 +0200 [thread overview]
Message-ID: <20150702200024.GF16529@breakpoint.cc> (raw)
In-Reply-To: <1435851533.11970.33.camel@edumazet-glaptop2.roam.corp.google.com>
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Thu, 2015-07-02 at 13:48 +0200, Florian Westphal wrote:
>
> > My plan:
> >
> > - move tee_active percpu varible to xtables core (suggested by Eric)
> > - in do_table, check if we're TEE'd or not
> >
> > 1. if no, then just use the jumpstack from offset 0 onwards.
> > 2. If yes, then fetch jumpstack, and use the upper half:
> >
> > if (__this_cpu_read(xt_tee_active))
> > jumpstack += private->stacksize;
>
> Or maybe not using a conditional
>
> jumpstack += private->stacksize * __this_cpu_read(xt_tee_active);
>
>
> BTW, I do not remember why I used a conditional in
> xt_write_recseq_begin(). This also adds extra setup cost, as @addend has
> to be preserved in the stack.
>
> Hmm... What about something like :
Hmm. I don't understand how this would work reliably.
xt_write_recseq_begin(); /* value is now odd */
/* other cpu fetches counters, blocks in read seeqlock */
for_each_rule( .. ) {
-> packet is sent by some target
/* reentry into do_table */
xt_write_recseq_begin(); /* value is now even */
-> other cpu unblocks since it thinks seqlock is taken
}
This is problematic because get_counters() (and thus the seqlock) seems
to be used as sync point with table replacement.
And reading Jans email, we can have re-entrancy in do_table() also
via -j REJECT and SYNPROXY, not just TEE :-/
MAYBE its worth investigating a dual stack approach.
Keep a small jumpstack on the local kernel stack
If table traverse exeeds it, switch to the private->jumpstack
This adds a conditional, but would avoid all the setup/restore/save for
most rulesets.
next prev parent reply other threads:[~2015-07-02 20:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 20:21 [PATCH nf] netfilter: arptables: use percpu jumpstack Florian Westphal
2015-07-02 11:30 ` Pablo Neira Ayuso
2015-07-02 11:48 ` Jan Engelhardt
2015-07-02 11:48 ` Florian Westphal
2015-07-02 15:38 ` Eric Dumazet
2015-07-02 20:00 ` Florian Westphal [this message]
2015-07-02 15:43 ` Pablo Neira Ayuso
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=20150702200024.GF16529@breakpoint.cc \
--to=fw@strlen.de \
--cc=eric.dumazet@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).