On Thu, 2005-12-08 at 15:45 -0800, Rohit Seth wrote: > > > Agreed. > > Though do we need to have full page allocated for each gdt (256 bytes) > then? ...possibly use kmalloc. > sorry, forgot about the false sharing part. -rohit - 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:
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Ravikiran G Thirumalai <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Rohit Seth <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Andi Kleen <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Rohit Seth <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Andi Kleen <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- From: Rohit Seth <[email protected]>
- Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- Prev by Date: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- Next by Date: Re: 2.6.15-rc4 panic in __nr_to_section() with CONFIG_SPARSEMEM
- Previous by thread: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
- Next by thread: Everyone Need This Linux-ia64
- Index(es):
 |