Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.

On Friday 30 November 2007 03:53:34 Arjan van de Ven wrote:
> On Mon, 26 Nov 2007 10:25:33 -0800
>
> > Agreed. On first glance, I was intrigued but:
> >
> > 1) Why is everyone so concerned that export symbol space is large?
> > 	- does it cost cpu or running memory?
>
> yes. about 120 bytes per symbol

But this patch makes that worse, not better.

> > 	- does it cause bugs?
>
> yes, bad apis are causing bugs... sys_open is just the starter of that.

Sure, but this doesn't change the APIs, either.  We seem to have fixed 
sys_open the right way, and since we're not supposed to care about 
out-of-tree modules...

Rusty.
-
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 RFC] [1/9] Core module symbol namespaces code and intro.
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
    • From: Stephen Hemminger <[email protected]>
  • Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: [PATCH] kexec: force x86_64 arches to boot kdump kernels on boot cpu
• Next by Date: Re: pnpacpi : exceeded the max number of IO resources
• Previous by thread: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
• Next by thread: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
• 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]