From: Greg KH <greg@kroah.com>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: "Bryan O'Sullivan" <bos@serpentine.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] 2.6.16-rc1 perfmon2 patch for review
Date: Wed, 25 Jan 2006 21:24:19 -0800 [thread overview]
Message-ID: <20060126052419.GB12538@kroah.com> (raw)
In-Reply-To: <20060126045510.GA10962@frankl.hpl.hp.com>
On Wed, Jan 25, 2006 at 08:55:10PM -0800, Stephane Eranian wrote:
> Greg,
>
> On Wed, Jan 25, 2006 at 03:52:04PM -0800, Greg KH wrote:
> > On Wed, Jan 25, 2006 at 12:08:13PM -0800, Bryan O'Sullivan wrote:
> > > 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.
> >
> > Yes, that is exactly right.
> >
> I don't have a problem moving the perfmon stuff to /sys, except for
> /proc/perfmon which is already being used by a bunch of tools. Unless
> we duplicate the information or use a simlink (if that's possible).
symlink will not work, sorry.
> Please indicate a location in the /sys tree where these would fit:
>
> /proc/perfmon
> /proc/perfmon_map
What are the contents of these files?
> These are currently sysctl():
>
> /proc/sys/kernel/perfmon/arg_size_max
> /proc/sys/kernel/perfmon/debug
> /proc/sys/kernel/perfmon/debug_ovfl
> /proc/sys/kernel/perfmon/expert_mode
> /proc/sys/kernel/perfmon/reset_stats
> /proc/sys/kernel/perfmon/smpl_buf_size_max
> /proc/sys/kernel/perfmon/sys_group
> /proc/sys/kernel/perfmon/task_group
>
What are the contents of these different files?
Remember that sysfs is one value per file, so sysctls translate usually
very easily to sysfs files.
You can always just use /sys/kernel/perfmon/ if you like, as I don't
think you are bound to anything that would be in the /sys/devices tree
(you don't export per-cpu statistics, right?)
Hope this helps,
greg k-h
next prev parent reply other threads:[~2006-01-26 5:26 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
2006-01-25 23:52 ` Greg KH
2006-01-26 4:55 ` Stephane Eranian
2006-01-26 5:24 ` Greg KH [this message]
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=20060126052419.GB12538@kroah.com \
--to=greg@kroah.com \
--cc=bos@serpentine.com \
--cc=eranian@hpl.hp.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