public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rohit Seth <rohit.seth@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: Ravikiran G Thirumalai <kiran@scalex86.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org,
	zach@vmware.com, shai@scalex86.org, nippung@calsoftinc.com
Subject: Re: [discuss] [patch] x86_64:  align and pad x86_64 GDT on page boundary
Date: Thu, 08 Dec 2005 15:50:43 -0800	[thread overview]
Message-ID: <1134085843.7131.55.camel@akash.sc.intel.com> (raw)
In-Reply-To: <1134085511.7131.53.camel@akash.sc.intel.com>

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


      parent reply	other threads:[~2005-12-08 23:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 19:42 [patch] x86_64: align and pad x86_64 GDT on page boundary Ravikiran G Thirumalai
2005-12-08 20:15 ` [discuss] " Andi Kleen
2005-12-08 21:55   ` Ravikiran G Thirumalai
2005-12-08 23:09     ` Rohit Seth
2005-12-08 23:11       ` Andi Kleen
2005-12-08 23:26         ` Rohit Seth
2005-12-08 23:26           ` Andi Kleen
2005-12-08 23:45             ` Rohit Seth
2005-12-08 23:43               ` Andi Kleen
2005-12-09 22:19                 ` Ravikiran G Thirumalai
2005-12-09 22:57                   ` Andi Kleen
2005-12-09 23:01                   ` Rohit Seth
2005-12-09 22:59                     ` Andi Kleen
2005-12-09 23:46                       ` Ravikiran G Thirumalai
2005-12-12  2:34                   ` Zwane Mwaikambo
2005-12-12  2:31                     ` Andi Kleen
2005-12-12  2:38                     ` Zwane Mwaikambo
2005-12-08 23:50               ` Rohit Seth [this message]

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=1134085843.7131.55.camel@akash.sc.intel.com \
    --to=rohit.seth@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nippung@calsoftinc.com \
    --cc=shai@scalex86.org \
    --cc=zach@vmware.com \
    /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