public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cliff Wickman <cpw@sgi.com>
To: Greg KH <gregkh@suse.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH V3] x86, UV: BAU performance and error recovery
Date: Fri, 28 May 2010 14:43:35 -0500	[thread overview]
Message-ID: <20100528194334.GA7707@sgi.com> (raw)
In-Reply-To: <20100528164725.GA29208@suse.de>


On Fri, May 28, 2010 at 09:47:25AM -0700, Greg KH wrote:
> On Fri, May 28, 2010 at 09:30:25AM -0700, H. Peter Anvin wrote:
> > On 05/28/2010 06:33 AM, Cliff Wickman wrote:
> > > - adds modification of tuning variables through /proc/sgi_uv
> > 
> > Adding new directories in /proc for a proprietary architecture is
> > frowned upon, to put it mildly.  At the very least try to find a place
> > in sysfs for it.
> > 
> > [Cc: gregkh in order to find a place in sysfs]
> 
> Hm, what type of files are you needing here?  Do they corrispond with
> any specific hardware devices?  If so, just put them on the hardware
> devices in sysfs.
> 
> thanks,
> 
> greg k-h

There is an SGI-specific directory in sysfs: /sys/firmware/sgi_uv
though the tuning variables for the handling of the hardware Broadcast
Assist Unit don't fit there very logically.  

The BAU's statistics are already displayed through the UV-only
/proc/sgi_uv/ptc_statistics.  This was deemed necessary because of the
potentially very large size of that file --- it is still true that a /sys file
is limited to one page, is it not?  We wanted to minimize the overhead
of the monitoring tools that read those statistics.
And the BAU tuning is related to those statistics.  That's why I chose
to put them along side, in /proc/sgi_uv/bau_tunables.
Even though it is a very small file.

Does that logic hold any water?

-Cliff
-- 
Cliff Wickman
SGI
cpw@sgi.com
(651) 683-3824

  reply	other threads:[~2010-05-28 19:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28 13:33 [PATCH V3] x86, UV: BAU performance and error recovery Cliff Wickman
2010-05-28 16:30 ` H. Peter Anvin
2010-05-28 16:47   ` Greg KH
2010-05-28 19:43     ` Cliff Wickman [this message]
2010-05-28 22:23       ` Greg KH
2010-05-28 23:36         ` Cliff Wickman
2010-05-29  0:05           ` Greg KH
2010-05-31 19:48             ` Cliff Wickman
2010-05-29  0:10           ` JD
2010-05-31 20:14             ` Cliff Wickman
  -- strict thread matches above, loose matches on Subject: below --
2010-05-31 21:52 Cliff Wickman
2010-06-01  7:19 ` Ingo Molnar
2010-05-31 19:49 Cliff Wickman
2010-05-25 17:02 Cliff Wickman
2010-05-28  9:33 ` Ingo Molnar

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=20100528194334.GA7707@sgi.com \
    --to=cpw@sgi.com \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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