From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 3/3] netfilter: ctnetlink: move event reporting for new entries outside the lock
Date: Mon, 16 Mar 2009 15:24:25 +0100 [thread overview]
Message-ID: <49BE6119.2050105@trash.net> (raw)
In-Reply-To: <49BE60D4.9040902@trash.net>
Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>> This patch moves the event reporting outside the lock section. With
>> this patch, the creation and update of entries is homogeneous from
>> the event reporting perspective. Moreover, as the event reporting is
>> done outside the lock section, the netlink broadcast delivery can
>> benefit of the yield() call under congestion.
>
> This one doesn't apply cleanly, probably because of the missing
> netlink_set_err patch. I've pushed out my current nf-next tree,
> please rediff against that tree.
It might also have been ordering, let me try again :)
next prev parent reply other threads:[~2009-03-16 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 16:07 [PATCH 1/3] netfilter: ctnetlink: cleanup master conntrack assignation Pablo Neira Ayuso
2009-03-05 16:07 ` [PATCH 2/3] netfilter: ctnetlink: cleanup conntrack update preliminary checkings Pablo Neira Ayuso
2009-03-16 14:27 ` Patrick McHardy
2009-03-05 16:07 ` [PATCH 3/3] netfilter: ctnetlink: move event reporting for new entries outside the lock Pablo Neira Ayuso
2009-03-16 14:23 ` Patrick McHardy
2009-03-16 14:24 ` Patrick McHardy [this message]
2009-03-16 14:28 ` Patrick McHardy
2009-03-16 14:26 ` [PATCH 1/3] netfilter: ctnetlink: cleanup master conntrack assignation Patrick McHardy
2009-03-18 16:42 ` Patrick McHardy
2009-03-18 22:26 ` Pablo Neira Ayuso
2009-03-18 22:35 ` Patrick McHardy
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=49BE6119.2050105@trash.net \
--to=kaber@trash.net \
--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.