mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: eranian@hpl.hp.com
Cc: Greg Kroah-Hartman <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] 2.6.16-rc1 perfmon2 patch for review
Date: Wed, 25 Jan 2006 12:08:13 -0800	[thread overview]
Message-ID: <1138219693.15295.13.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <20060124150912.GB7130@frankl.hpl.hp.com>

On Tue, 2006-01-24 at 07:09 -0800, Stephane Eranian wrote:

> Because I tried regrouping all the /proc AND related interface into a single
> C file.

sysctls seem to be every bit as deprecated as /proc for what you are
tring to do.

> Well, it is not clear to me what criteria is used for /sys vs /proc.

My understanding is that only process-related stuff belongs in /proc
now.  Other random cruft that has accumulated over the years is left
there for backwards compatibility, but /sys interfaces are the way
forward now.

Some interfaces have already moved out of /proc in part or in whole, so
for example some ACPI functionality remains in /proc, while other bits
have moved to /sys/power.

The perfmon stuff may belong in a new hierarchy, for example
like /sys/class/pfm, or perhaps in /sys/devices/system/cpu.  Someone
like Greg K-H can put you to rights there.

	<b


  reply	other threads:[~2006-01-25 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 15:20 Stephane Eranian
2006-01-20 16:47 ` Bryan O'Sullivan
2006-01-24 15:09   ` Stephane Eranian
2006-01-25 20:08     ` Bryan O'Sullivan [this message]
2006-01-25 23:52       ` Greg KH
2006-01-26  4:55         ` Stephane Eranian
2006-01-26  5:24           ` Greg KH
2006-01-26  5:43             ` Stephane Eranian
2006-01-26 18:23               ` Bryan O'Sullivan
2006-01-27  0:14               ` Greg KH

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=1138219693.15295.13.camel@serpentine.pathscale.com \
    --to=bos@serpentine.com \
    --cc=eranian@hpl.hp.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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