From: Andrew Morton <akpm@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.6.7-mm5] perfctr low-level documentation
Date: Sat, 3 Jul 2004 03:34:13 -0700 [thread overview]
Message-ID: <20040703033413.239d58d8.akpm@osdl.org> (raw)
In-Reply-To: <200407031028.i63AS9W3018392@harpo.it.uu.se>
Mikael Pettersson <mikpe@csd.uu.se> wrote:
>
> On Fri, 2 Jul 2004 15:44:14 -0700, Andrew Morton wrote:
> >Mikael Pettersson <mikpe@csd.uu.se> wrote:
> >>
> >> I'm
> >> considering Christoph Hellwig's suggestion of moving
> >> the API back to /proc/<pid>/, but with multiple files
> >> and open/read/write/mmap instead of ioctl. I believe I
> >> can make that work, but it would take a couple of days
> >> to implement properly. Please indicate if you would like
> >> this change or not.
> >
> >What would be the advantages of such a change?
>
> Eliminating the 6 or so new syscalls I was forced
> to add when nuking the old ioctl() API.
syscalls are cheap.
> There would be a /proc/<pid>/<tid>/perfctr/ directory
> with files representing the control data, counter
> state, general info, and auxiliary control ops.
Futzing around with /proc handlers and mmapping /proc files doesn't sound
very attractive. Unless we have some solid reason for changing things
I'd be inclined to leave it as-is. Do you agree?
next prev parent reply other threads:[~2004-07-03 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 10:28 [PATCH][2.6.7-mm5] perfctr low-level documentation Mikael Pettersson
2004-07-03 10:34 ` Andrew Morton [this message]
2004-07-03 14:08 ` small perfctr bug or misunderstanding bert hubert
-- strict thread matches above, loose matches on Subject: below --
2004-07-03 14:56 [PATCH][2.6.7-mm5] perfctr low-level documentation Mikael Pettersson
2004-07-02 19:19 Mikael Pettersson
2004-07-02 22:44 ` Andrew Morton
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=20040703033413.239d58d8.akpm@osdl.org \
--to=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.