public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Christoph Lameter <clameter@sgi.com>,
	torvalds@osdl.org, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: move-accounting-function-calls-out-of-critical-vm-code-paths.patch
Date: Mon, 07 Feb 2005 06:11:48 -0800	[thread overview]
Message-ID: <42077724.1060606@sgi.com> (raw)
In-Reply-To: <20050203150551.4d88f210.akpm@osdl.org>

Andrew Morton wrote:
> Christoph Lameter <clameter@sgi.com> wrote:
> 
>>I hope that Roland's changes for higher resolution of cputime would
>>make that possible. But this is Jay's thing not mine. I just want to make
>>sure that the CSA patches does not get in the way of our attempts to
>>improve the performance of the page fault handler. In the discussions on
>>linux-mm there was also some concern about adding these calls.
> 
> 
> Well your patch certainly cleans things up in there and would be a good
> thing to have as long as we can be sure that it doesn't break the
> accounting in some subtle way.
> 
> Which implies that we need to see some additional accounting code, so we
> can verify that the base accumulation infrastructure is doing the expected
> thing.  As well as an ack from the interested parties.  Does anyone know
> what's happening with all the new accounting initiatives?  I'm seeing no
> activity at all.

Sorry guys! I have been away for three weeks on short term disability.:(

I have tested Christoph's patch before the leave. It did work for CSA
and showed performance improvement on certain configuration.

CSA is currently implemented as a loadable module. I think ELSA is the
same, right? The use of the enhanced accounting data collection
code is not in the kernel tree. That was why Andrew did not see usage of 
the accounting patches. Should i propose to include the CSA module in
the kernel then, Andrew? :)

Cheers,
  - jay



  parent reply	other threads:[~2005-02-07 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050110184617.3ca8d414.akpm@osdl.org>
     [not found] ` <Pine.LNX.4.58.0502031319440.25268@schroedinger.engr.sgi.com>
     [not found]   ` <20050203140904.7c67a144.akpm@osdl.org>
2005-02-03 22:45     ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Christoph Lameter
2005-02-03 23:05       ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Andrew Morton
2005-02-04  0:41         ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Tim Schmielau
2005-02-04  7:38           ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Guillaume Thouvenin
2005-02-07 14:11         ` Jay Lan [this message]
2005-02-07 22:57           ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Andrew Morton
2005-02-08 10:11           ` move-accounting-function-calls-out-of-critical-vm-code-paths.patch Guillaume Thouvenin
2005-02-03 21:22 move-accounting-function-calls-out-of-critical-vm-code-paths.patch Christoph Lameter

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=42077724.1060606@sgi.com \
    --to=jlan@sgi.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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