mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] performance counters 3.1 for 2.5.45 [4/4]: kernel changes
Date: 04 Nov 2002 12:56:36 -0800	[thread overview]
Message-ID: <1036443396.18668.16.camel@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <15814.55581.459295.2217@kim.it.uu.se>

On Mon, 2002-11-04 at 12:31, Mikael Pettersson wrote:
> Stephen Hemminger writes:
>  > On Thu, 2002-10-31 at 15:10, Mikael Pettersson wrote:
>  > > This is part 4 of 4 of perfctr-3.1 for the 2.5.45 kernel:
>  > > kernel changes to integrate the low and high-level drivers.
> ...
>  > 
>  > Rather than adding yet another system call, shouldn't this be done by
>  > extending the cpu part of sysfs (or /proc)?
> 
> Why?
> ptrace() is a system call
> fork() is a system call
> write() is a system call
> other arch's performance counter interfaces are system calls
> ...

ptrace predates /proc, and /proc is gradually superseding ptrace.
Eventually it is hoped that ptrace dies.

Other architecture's added performance counters back in 2.4 before sysfs
was added.

The reason to use a file system rather than a syscall is so that
standard tools like sh, awk, perl, ... can be used on the data without
having to build a separate command to access the data.

Linus is more likely to adopt simpler logical interfaces.



      reply	other threads:[~2002-11-04 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 23:10 Mikael Pettersson
2002-11-04 20:12 ` Stephen Hemminger
2002-11-04 20:31   ` Mikael Pettersson
2002-11-04 20:56     ` Stephen Hemminger [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=1036443396.18668.16.camel@dell_ss3.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®