From: Cliff Wickman <cpw@sgi.com>
To: JD <jd1008@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] x86, UV: BAU performance and error recovery
Date: Mon, 31 May 2010 15:14:24 -0500 [thread overview]
Message-ID: <20100531201424.GA6259@sgi.com> (raw)
In-Reply-To: <4C005B6C.4090006@gmail.com>
On Fri, May 28, 2010 at 05:10:20PM -0700, JD wrote:
>
>
> On 05/28/2010 04:36 PM, Cliff Wickman wrote:
>> On Fri, May 28, 2010 at 03:23:21PM -0700, Greg KH wrote:
>>
>>> On Fri, May 28, 2010 at 02:43:35PM -0500, Cliff Wickman wrote:
>>>
>>>> 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?
>>>>
>>> It is limited to one single value, which would never be larger than a
>>> page, so yes, it is limited to one page.
>>>
>>> What kind of information are you showing here? Should this thing just
>>> be in debugfs instead? You can do whatever you want there.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>> /proc/sgi_uv/bau_tunables would be a read/write file to display and change
>> nine threshold and delay values for tuning the BAU driver.
>>
>> I like debugfs, except that a distro may not build the kernel with it
>> configured on. The tunables should be available as administrative
>> options on a customer kernel, not just as a development tool.
>>
>> And in our case the distros are already building with other such writable
>> options in /proc/sgi_uv. We'd like to postpone a wholesale move of such
>> options (assuming there will be some better place) and stay with the existing
>> location for this release.
>>
>> I know we (the community) would like to move non-process info out of /proc.
>> It seems to me that we need a similar filesystem for large and/or
>> administrative files. That's my perspective.
>>
>> -Cliff
>>
> Would the similar filesystem you propose be backed by permanent storage,
> unlike /proc?
I withdraw my proposal for any new filesystem type, as debugfs works fine
for what I'm talking about, as long as it is configured on by all the
distributions.
No, a permanent storage backed filesystem was not what I had in mind.
--
Cliff Wickman
SGI
cpw@sgi.com
(651) 683-3824
next prev parent reply other threads:[~2010-05-31 20:14 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
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 [this message]
-- 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=20100531201424.GA6259@sgi.com \
--to=cpw@sgi.com \
--cc=jd1008@gmail.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