Re: [PATCH 3/3] netlink: use a statically allocated nl_table instead

From: Denis Cheng <[email protected]>
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 <[email protected]>

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/3] netlink: use the macro min(x,y) provided by <linux/kernel.h> instead
    • From: Denis Cheng <[email protected]>
  • [PATCH 2/3] netlink: the temp variable name max is ambiguous
    • From: Denis Cheng <[email protected]>
  • [PATCH 3/3] netlink: use a statically allocated nl_table instead
    • From: Denis Cheng <[email protected]>

• Prev by Date: Re: [PATCH]PCI:disable resource decode in PCI BAR detection
• Next by Date: Re: [PATCH] net/ipv4/af_inet.c: use ARRAY_SIZE macro from kernel.h instead
• Previous by thread: [PATCH 3/3] netlink: use a statically allocated nl_table instead
• Next by thread: Re: [PATCH 2/3] netlink: the temp variable name max is ambiguous
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]