From: Patrick McHardy <kaber@trash•net>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Jorrit Kronjee <j.kronjee@infopact•nl>,
netfilter-devel@vger•kernel.org, netdev <netdev@vger•kernel.org>
Subject: Re: [PATCH nf-next-2.6] xt_hashlimit: RCU conversion
Date: Thu, 01 Apr 2010 13:03:29 +0200 [thread overview]
Message-ID: <4BB47D81.3060400@trash.net> (raw)
In-Reply-To: <1270038210.2103.23.camel@edumazet-laptop>
Eric Dumazet wrote:
> xt_hashlimit uses a central lock per hash table and suffers from
> contention on some workloads. (Multiqueue NIC or if RPS is enabled)
>
> After RCU conversion, central lock is only used when a writer wants to
> add or delete an entry.
>
> For 'readers', updating an existing entry, they use an individual lock
> per entry.
Looks good to me, thanks Eric.
> -/* allocate dsthash_ent, initialize dst, put in htable and lock it */
> -static struct dsthash_ent *
> -dsthash_alloc_init(struct xt_hashlimit_htable *ht,
> - const struct dsthash_dst *dst)
Is there a reason for moving this function downwards in the file?
That unnecessarily increases the diff and makes the patch harder to
review. For review purposes I moved it back up, resulting in 42
lines less diff.
next prev parent reply other threads:[~2010-04-01 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BA74950.6000305@infopact.nl>
[not found] ` <4BA7A5D8.5080101@trash.net>
[not found] ` <4BA8DAC5.6050002@infopact.nl>
[not found] ` <1269364893.2983.296.camel@edumazet-laptop>
[not found] ` <4BAA2DC5.7000409@infopact.nl>
[not found] ` <1269447674.3213.64.camel@edumazet-laptop>
2010-03-25 9:32 ` debugging kernel during packet drops Eric Dumazet
2010-03-25 10:35 ` Patrick McHardy
2010-03-25 11:02 ` Eric Dumazet
2010-03-31 12:23 ` [PATCH nf-next-2.6] xt_hashlimit: RCU conversion Eric Dumazet
2010-04-01 11:03 ` Patrick McHardy [this message]
2010-04-01 12:10 ` Eric Dumazet
2010-04-01 12:36 ` Patrick McHardy
2010-03-25 12:42 ` debugging kernel during packet drops Jan Engelhardt
2010-03-30 12:06 ` Jan Engelhardt
2010-03-30 14:12 ` 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=4BB47D81.3060400@trash.net \
--to=kaber@trash$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=j.kronjee@infopact$(echo .)nl \
--cc=netdev@vger$(echo .)kernel.org \
--cc=netfilter-devel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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