From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Cc: netfilter-devel@vger.kernel.org, Liping Zhang <zlpnobody@gmail.com>
Subject: Re: [PATCH v4] xtables: Add an interval option for xtables lock wait
Date: Thu, 23 Jun 2016 20:44:01 +0200 [thread overview]
Message-ID: <20160623184401.GA12620@salvia> (raw)
In-Reply-To: <1465957673-1637-1-git-send-email-subashab@codeaurora.org>
Hi Subash,
On Tue, Jun 14, 2016 at 08:27:53PM -0600, Subash Abhinov Kasiviswanathan wrote:
> ip[6]tables currently waits for 1 second for the xtables lock to be
> freed if the -w option is used. We have seen that the lock is held
> much less than that resulting in unnecessary delay when trying to
> acquire the lock. This problem is even severe in case of latency
> sensitive applications.
>
> Introduce a new option 'W' to specify the wait interval in decimal
> format [seconds.microseconds]. If this option is not specified,
> the command sleeps for 1 second by default.
Compilation breaks with this patch:
xtables.c: In function ‘do_parse’:
xtables.c:1029:8: error: ‘restore’ undeclared (first use in this function)
if (restore) {
^
xtables.c:1029:8: note: each undeclared identifier is reported only once for each function it appears in
Makefile:778: recipe for target 'xtables_compat_multi-xtables.o' failed
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-23 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 2:27 [PATCH v4] xtables: Add an interval option for xtables lock wait Subash Abhinov Kasiviswanathan
2016-06-23 18:44 ` Pablo Neira Ayuso [this message]
2016-06-24 0:39 ` subashab
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=20160623184401.GA12620@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=subashab@codeaurora.org \
--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 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.