public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	clameter@sgi.com, rmk@arm.linux.org.uk,
	linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com
Subject: Re: [PATCH 1/2] Define new percpu interface for shared data -- version 3
Date: Wed, 23 May 2007 12:31:53 -0700	[thread overview]
Message-ID: <20070523123153.c4f8c7e6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070523192005.GB4072@localhost.localdomain>

On Wed, 23 May 2007 12:20:05 -0700 Ravikiran G Thirumalai <kiran@scalex86.org> wrote:

> On Wed, May 23, 2007 at 12:09:56PM -0700, Yu, Fenghua wrote:
> > 
> > >Has there been any measurable benefit yet due to tail padding?
> > 
> > We don't have data that tail padding actually helps. It all
> > depends on what data the linker lays out in the cachelines.
> > 
> > As of now we just want to create the infrastructure (so that
> > more and more people who need it, can use it).
> 
> So what we have now is space wastage on some architectures, space savings on
> some, but with no measurable performance benefit due to the infrastructure
> itself.  Why not push the infrastructure when we really need it, as against
> pushing it now when we are not sure if it benefits?
> 

It makes sense from a theoretical POV and is pretty much a no-op in terms
of resource consumption.

The problem with the wait-until-it-hurts approach is that by the time
someone hurts from this and we find out about it, they may well be using
some year-old enterprise kernel and it's too late to fix it for them.


  reply	other threads:[~2007-05-23 19:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 12:47 is TIF_NOTIFY_RESUME used? Stephane Eranian
2007-05-22 16:02 ` Andrew Morton
2007-05-22 16:07   ` Stephane Eranian
2007-05-22 16:15     ` Andrew Morton
2007-05-22 22:51       ` Stephane Eranian
2007-05-22 23:02         ` Andrew Morton
2007-05-23  9:57           ` [PATCH] remove unused TIF_NOTIFY_RESUME flag Stephane Eranian
2007-05-22 18:20   ` [PATCH 1/2] Define new percpu interface for shared data -- version 3 Fenghua Yu
2007-05-23 17:49     ` Andrew Morton
2007-05-23 18:26       ` Yu, Fenghua
2007-05-23 18:57         ` Ravikiran G Thirumalai
2007-05-23 19:09           ` Yu, Fenghua
2007-05-23 19:20             ` Ravikiran G Thirumalai
2007-05-23 19:31               ` Andrew Morton [this message]
2007-05-23 21:13                 ` Yu, Fenghua
2007-05-25  9:43                   ` Russell King
2007-05-25 15:24                     ` Yu, Fenghua
2007-05-24  9:03           ` Martin Schwidefsky
2007-05-24 10:16             ` Ravikiran G Thirumalai

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=20070523123153.c4f8c7e6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=fenghua.yu@intel.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=schwidefsky@de.ibm.com \
    --cc=suresh.b.siddha@intel.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