From: Joe Perches <joe@perches.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Tom Herbert <therbert@google.com>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH v2 nf-next] netfilter: conntrack: remove the central spinlock
Date: Wed, 22 May 2013 13:38:24 -0700 [thread overview]
Message-ID: <1369255104.2143.108.camel@joe-AO722> (raw)
In-Reply-To: <1369253761.3301.355.camel@edumazet-glaptop>
On Wed, 2013-05-22 at 13:16 -0700, Eric Dumazet wrote:
> On Wed, 2013-05-22 at 12:57 -0700, Joe Perches wrote:
> > It might also be nice to mark it if ever more than a u16
> > brace/flock/coven/cluster worth of cpus become feasible
> > as it seems int is used almost everywhere else.
>
> It seems Linus hates cpu_t or whatever_t
Go figure.
> Thats why we have u16 everywhere to code cpu numbers, and why we use
> "unsigned long" for jiffies.
u16 for cpu is hardly used at all.
$ git grep -E "^\s*\w+\s+cpu\s*;" | cut -f2- -d":" | \
sed -r -e 's/^\s+//g' -e 's/\s+/ /g' -e 's/;.*//' | \
sort | uniq -c | sort -rn
569 int cpu
29 return cpu
28 __u32 cpu
14 u32 cpu
7 unsigned cpu
5 u16 cpu
4 cpuid_t cpu
3 uint32_t cpu
2 __u8 cpu
2 u64 cpu
2 s32 cpu
2 long cpu
1 u8 cpu
1 __u16 cpu
1 struct cpu
1 short cpu
1 __le32 cpu
1 geo_cpu_t cpu
> So far, I believe linux supports at most 4096 cpus.
I believe that as well.
next prev parent reply other threads:[~2013-05-22 20:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 3:04 [PATCH nf-next] netfilter: conntrack: remove the central spinlock Eric Dumazet
2013-05-09 5:43 ` Cong Wang
2013-05-09 6:01 ` Eric Dumazet
2013-05-09 7:46 ` Cong Wang
2013-05-09 13:46 ` Eric Dumazet
2013-05-22 17:47 ` [PATCH v2 " Eric Dumazet
2013-05-22 18:20 ` Joe Perches
2013-05-22 19:26 ` Eric Dumazet
2013-05-22 19:57 ` Joe Perches
2013-05-22 20:16 ` Eric Dumazet
2013-05-22 20:38 ` Joe Perches [this message]
2013-05-22 20:48 ` Eric Dumazet
2013-05-22 21:12 ` Joe Perches
2013-05-22 21:29 ` David Miller
2013-05-22 21:34 ` Eric Dumazet
2013-05-24 13:16 ` Jesper Dangaard Brouer
2013-05-24 13:51 ` Eric Dumazet
2013-05-27 12:33 ` Jesper Dangaard Brouer
2013-05-27 12:36 ` Pablo Neira Ayuso
2013-08-23 14:42 ` Jesper Dangaard Brouer
2013-08-26 22:28 ` Pablo Neira Ayuso
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=1369255104.2143.108.camel@joe-AO722 \
--to=joe@perches.com \
--cc=eric.dumazet@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=therbert@google.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.