From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/3] netfilter: speed up netns cleanup
Date: Mon, 1 May 2017 21:37:25 +0200 [thread overview]
Message-ID: <20170501193725.GA24460@breakpoint.cc> (raw)
In-Reply-To: <20170501092036.GA3476@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> On Mon, Apr 24, 2017 at 03:37:38PM +0200, Florian Westphal wrote:
> > low hanging fruits to speed up netns cleanup in netfilter.
> > We're way too happy to issue expensive synchronize_rcu() all
> > over the place.
> >
> > On my test vm 8 processes doing 32 unshare each finish in ~3 minutes,
> > with these patches it gets down to 40 seconds.
>
> If this is a script, can we place this somewhere to keep an eye on
> this?
It was based on Andreys sample program but this is enough actually
to show the difference:
time for x in $(seq 1 100); do unshare -n /bin/true;done
prev parent reply other threads:[~2017-05-01 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 13:37 [PATCH nf-next 0/3] netfilter: speed up netns cleanup Florian Westphal
2017-04-24 13:37 ` [PATCH nf-next 1/3] netfilter: batch synchronize_net calls during hook unregister Florian Westphal
2017-04-24 13:37 ` [PATCH nf-next 2/3] netfilter: nf_log: don't call synchronize_rcu in nf_log_unset Florian Westphal
2017-04-25 6:33 ` Liping Zhang
2017-04-24 13:37 ` [PATCH nf-next 3/3] netfilter: nf_queue: only call synchronize_net twice if nf_queue is active Florian Westphal
2017-04-25 8:24 ` [PATCHo nf-next v2] netfilter: nf_log: don't call synchronize_rcu in nf_log_unset Florian Westphal
2017-05-01 9:20 ` [PATCH nf-next 0/3] netfilter: speed up netns cleanup Pablo Neira Ayuso
2017-05-01 19:37 ` Florian Westphal [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=20170501193725.GA24460@breakpoint.cc \
--to=fw@strlen.de \
--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 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.