From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org, Liping Zhang <zlpnobody@gmail.com>
Subject: Re: [PATCH iptables V2 2/2] xshared: using the blocking file lock request when we wait indefinitely
Date: Tue, 28 Feb 2017 12:18:12 +0100 [thread overview]
Message-ID: <20170228111812.GB17105@salvia> (raw)
In-Reply-To: <1486381667-32577-1-git-send-email-zlpnobody@163.com>
On Mon, Feb 06, 2017 at 07:47:47PM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> When using "-w" to avoid concurrent instances, we try to do flock() every
> one second until it success. But one second maybe too long in some
> situations, and it's hard to select a suitable interval time. So when
> using "iptables -w" to wait indefinitely, it's better to block until
> it become success.
>
> Now do some performance tests. First, flush all the iptables rules in
> filter table, and run "iptables -w -S" endlessly:
> # iptables -F
> # iptables -X
> # while : ; do
> iptables -w -S >&- &
> done
>
> Second, after adding and deleting the iptables rules 100 times, measure
> the time cost:
> # time for i in $(seq 100); do
> iptables -w -A INPUT
> iptables -w -D INPUT
> done
>
> Before this patch:
> real 1m15.962s
> user 0m0.224s
> sys 0m1.475s
>
> Apply this patch:
> real 0m1.830s
> user 0m0.168s
> sys 0m1.130s
Also applied, thanks.
prev parent reply other threads:[~2017-02-28 11:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 11:47 [PATCH iptables V2 2/2] xshared: using the blocking file lock request when we wait indefinitely Liping Zhang
2017-02-28 11:18 ` Pablo Neira Ayuso [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=20170228111812.GB17105@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@gmail.com \
/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).