From: Eric Dumazet <dada1@cosmosbay.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/4] NET : struct proto diet
Date: Mon, 05 Nov 2007 18:52:32 +0100 [thread overview]
Message-ID: <472F5860.4010607@cosmosbay.com> (raw)
Hi
After reading David's machines have NR_CPUS set to 4096, I realized how
fat was 'struct proto', since it uses a stats[NR_CPUS] field to keep
track of inuse sockets per protocol.
With NR_CPUS = 4096, this means we allocate 4096*SMP_CACHE_BYTES bytes
per 'struct proto'.
As these structures are static (data section of kernel), this grows data
kernel section by 256 KB per protocol.
This patch series does some cleanup and optimization.
[PATCH 1/4] NET : defines an infrastructure to keep 'inuse' changes in
an efficent SMP/NUMA way.
[PATCH 2/4] NET : makes ipv4 use the {DEFINE|REF}_PROTO_INUSE
infrastructure
[PATCH 3/4] NET : makes ipv6 use the {DEFINE|REF}_PROTO_INUSE
infrastructure
[PATCH 4/4] NET : makes sctp use the {DEFINE|REF}_PROTO_INUSE
infrastructure
Thank you
Eric
next reply other threads:[~2007-11-05 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:52 Eric Dumazet [this message]
2007-11-06 7:43 ` [PATCH 0/4] NET : struct proto diet David Miller
2007-11-07 16:16 ` [PATCH 0/2] generalize {DEFINE|REF}_PROTO_INUSE was " Arnaldo Carvalho de Melo
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=472F5860.4010607@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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).