From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: fweisbec@gmail.com, paulus@samba.org, tglx@linutronix.de,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, jens.axboe@oracle.com
Subject: Re: [PATCH 0/2]: Get perf counters working on D-cache aliasing cpus.
Date: Tue, 08 Sep 2009 05:38:28 -0700 (PDT) [thread overview]
Message-ID: <20090908.053828.161377056.davem@davemloft.net> (raw)
In-Reply-To: <20090908123610.GA3515@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Tue, 8 Sep 2009 14:36:10 +0200
> The only (small) worry would be that this uses vmalloc space on
> 32-bit platforms which is generally a scarce resource.
Yes, I considered this too.
But as you said there are things that mitigate how much of
a real issue this actually is.
next prev parent reply other threads:[~2009-09-08 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 12:10 [PATCH 0/2]: Get perf counters working on D-cache aliasing cpus David Miller
2009-09-08 12:36 ` Ingo Molnar
2009-09-08 12:38 ` David Miller [this message]
2009-09-18 12:31 ` Peter Zijlstra
2009-09-18 17:22 ` David Miller
2009-09-18 17:26 ` Peter Zijlstra
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=20090908.053828.161377056.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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