From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: mikpe@csd.uu.se, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][1/6] perfctr-2.7.3 for 2.6.7-rc1-mm1: core
Date: Tue, 22 Jun 2004 02:14:41 -0700 [thread overview]
Message-ID: <20040622021441.4f6aa13c.akpm@osdl.org> (raw)
In-Reply-To: <20040622091219.GA32146@infradead.org>
Christoph Hellwig <hch@infradead.org> wrote:
>
> On Tue, Jun 22, 2004 at 02:04:17AM -0700, Andrew Morton wrote:
> > Christoph Hellwig <hch@infradead.org> wrote:
> > >
> > > On Tue, Jun 22, 2004 at 01:53:11AM -0700, Andrew Morton wrote:
> > > > Also there should be a document or a manpage or something which describes,
> > > > in detail:
> > > >
> > > > - the user/kernel API (separate document, probably)
> > >
> > > It also needs moving back to /proc/<pid>/ files from the syscall API.
> >
> > What does this mean?
>
> Early version of perfctr used files in /proc/<pid>/ for controlling perfctr
> instead of the syscalls, and indeed that's a much better fit for most of them.
> Let's ressurect that code instead of doing the syscall approach.
This appears to have come out of the blue. Please explain why you think
this change is needed.
next prev parent reply other threads:[~2004-06-22 9:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 22:18 Mikael Pettersson
2004-06-22 8:53 ` Andrew Morton
2004-06-22 8:59 ` Christoph Hellwig
2004-06-22 9:04 ` Andrew Morton
2004-06-22 9:12 ` Christoph Hellwig
2004-06-22 9:14 ` Andrew Morton [this message]
2004-06-22 9:18 ` Christoph Hellwig
2004-06-22 9:20 ` Andrew Morton
2004-06-22 14:38 ` Mikael Pettersson
2004-06-22 17:20 ` Christoph Hellwig
2004-06-22 20:35 ` Mikael Pettersson
2004-06-22 13:47 ` Mikael Pettersson
2004-06-22 19:18 ` Andrew Morton
2004-06-22 13:59 ` Mikael Pettersson
2004-06-22 19:22 ` Andrew Morton
[not found] <223si-461-9@gated-at.bofh.it>
[not found] ` <29Piu-4H4-27@gated-at.bofh.it>
2004-06-22 10:21 ` Andi Kleen
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=20040622021441.4f6aa13c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
Powered by JetHome