From: Stephane Eranian <eranian@hpl.hp.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
perfmon@napali.hpl.hp.com
Subject: Re: perfmon2 vector argument question
Date: Fri, 30 Jun 2006 03:24:35 -0700 [thread overview]
Message-ID: <20060630102435.GA21819@frankl.hpl.hp.com> (raw)
In-Reply-To: <20060628201708.08af034c.akpm@osdl.org>
Andrew,
On Wed, Jun 28, 2006 at 08:17:08PM -0700, Andrew Morton wrote:
> >
> > Does someone have something else to propose?
> >
> > If not, what is your opinion of the two approaches above?
> >
>
> The first approach should be fine - we do that in lots of places, such as
> in core_sys_select().
>
Ok, that's good to know. I looked at the stack consumption on x86 and it
is comparable to what you do for core_sys_select().
> Applications mut be calling this thing at a heck of a rate for kfree()
> overhead to matter. I trust CONFIG_DEBUG_SLAB wasn't turned on...
That was using a micro-benchmark to stress certain paths in perfmon.
CONFIG_DEBUG_SLAB was not turned on.
Thanks.
--
-Stephane
prev parent reply other threads:[~2006-06-30 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 20:40 perfmon2 vector argument question Stephane Eranian
2006-06-29 3:17 ` Andrew Morton
2006-06-30 10:24 ` Stephane Eranian [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=20060630102435.GA21819@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perfmon@napali.hpl.hp.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