LKML Archive on
help / color / mirror / Atom feed
From: Andrew Morton <>
To: Mikael Pettersson <>
Subject: Re: [PATCH][1/7] perfctr-2.7.2 for 2.6.6-mm2: core
Date: Fri, 14 May 2004 15:59:07 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mikael Pettersson <> wrote:
> - core driver files and kernel changes

Looks like we need six system calls if we're going to do it that way.

All that marshalling and unmarshalling code is a bit evil.  I wonder if
there's some way in which it can be flattened out.

One option would be to present all the info to userspace as a virtual
filesystem, although it would be a bit weird that the contents of the
"files" depends upon the process which reads them.

Maybe a mkdir() on that filesystem could create a directory which contains
files which contain the counters for the process which made the directory? 
The directory would need to be auto-rmdir'ed on process exit.  It's
basically the same semantics as /proc/pid.

But /proc/pid can be read by processes other than "pid".  Does the same
apply to the perfcntr instrumentation?  (Being able to read another
process's perfcntr info sounds useful.  Is it?)

  parent reply	other threads:[~2004-05-14 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-14 14:09 Mikael Pettersson
2004-05-14 14:40 ` Christoph Hellwig
2004-05-14 22:59 ` Andrew Morton [this message]
2004-05-15 14:39 Mikael Pettersson
2004-05-15 14:40 Mikael Pettersson
2004-05-16  5:39 ` Andrew Morton
2004-05-16 11:52 Mikael Pettersson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [PATCH][1/7] perfctr-2.7.2 for 2.6.6-mm2: core' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).