public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Move perfmon tables from thread_struct to pfm_context
Date: Tue, 29 Aug 2006 19:55:03 +0000	[thread overview]
Message-ID: <20060829125502.A24069@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060829110856.A23515@unix-os.sc.intel.com>

On Tue, Aug 29, 2006 at 08:55:28PM +0100, Christoph Hellwig wrote:
> On Tue, Aug 29, 2006 at 11:08:56AM -0700, Keshavamurthy Anil S wrote:
> > This patch renders thread_struct->pmcs[] and thread_struct->pmds[]
> > OBSOLETE. The actual table is moved to pfm_context structure which 
> > is the right thing to do. Also this will in future avoid KABI breakages
> > for the distro as well when the table size changes.
> 
> NACK.  There is no such thing as a KABI, and any patch the claims to
> help towards it will automatically be rejected.  You should get a doctor
> to help you stop seeing things like that.
You have not fully understood the benifit of this patch. Moving pmds[] and pmcs[]
away from thread_struct saves that much space from the thread_struct
and in turns saves that much spaces from the task_struct. Again by moving
this table to pfm_context makes it possible that this table space is 
created only when pfm_context_alloc() is called which is 
when this is really required. This patch in fact reduces the sizeof task_struct
and their by allowing that extra space for the kernel stacks use :)

Please relook at the benifits of this patch again.

-Anil

  reply	other threads:[~2006-08-29 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 18:08 Move perfmon tables from thread_struct to pfm_context Keshavamurthy Anil S
2006-08-29 19:55 ` Keshavamurthy Anil S [this message]
2006-08-29 19:55 ` Christoph Hellwig
2006-08-29 21:29 ` Stephane Eranian

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=20060829125502.A24069@unix-os.sc.intel.com \
    --to=anil.s.keshavamurthy@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    /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