From: David Miller <davem@davemloft.net>
To: crquan@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, cr_quan@163.com
Subject: Re: [PATCH 3/3] netlink: use a statically allocated nl_table instead
Date: Sun, 16 Sep 2007 16:38:14 -0700 (PDT) [thread overview]
Message-ID: <20070916.163814.77649402.davem@davemloft.net> (raw)
In-Reply-To: <11886759772663-git-send-email-crquan@gmail.com>
From: Denis Cheng <crquan@gmail.com>
Date: Sun, 2 Sep 2007 03:45:59 +0800
> if the table is always fixed size with MAX_LINKS entries, why not use a statically
> allocated table straightforwardly?
>
> Signed-off-by: Denis Cheng <crquan@gmail.com>
I made the explicit decision to dynamically allocate because
many systems have limits on how large the kernel image can
be and therefore the less we statically allocate huge tables
(constant size or not) the better.
Lockdep is the worst offender, for example, it's completely awful. It
consumes 4MB of kernel BSS space when enabled on a 64-bit platform.
Patch not applied.
next prev parent reply other threads:[~2007-09-16 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 19:45 [PATCH 1/3] netlink: use the macro min(x,y) provided by <linux/kernel.h> instead Denis Cheng
2007-09-01 19:45 ` [PATCH 2/3] netlink: the temp variable name max is ambiguous Denis Cheng
2007-09-01 19:45 ` [PATCH 3/3] netlink: use a statically allocated nl_table instead Denis Cheng
2007-09-16 23:38 ` David Miller [this message]
2007-09-16 23:36 ` [PATCH 2/3] netlink: the temp variable name max is ambiguous David Miller
2007-09-20 16:56 ` rae l
[not found] ` <46DA07B8.4050204@davidnewall.com>
2007-09-02 0:56 ` [PATCH 1/3] netlink: use the macro min(x,y) provided by <linux/kernel.h> instead rae l
2007-09-16 23:35 ` David Miller
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=20070916.163814.77649402.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cr_quan@163.com \
--cc=crquan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).