From: "Bert Wesarg" <bert.wesarg@googlemail.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Paul Jackson" <pj@sgi.com>,
travis@sgi.com, mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] x86: add cpus_scnprintf function v3
Date: Thu, 10 Apr 2008 19:36:12 +0200 [thread overview]
Message-ID: <36ca99e90804101036o407dda7dyc303bd87f46c5cfc@mail.gmail.com> (raw)
In-Reply-To: <20080410173016.GA28068@suse.de>
On Thu, Apr 10, 2008 at 7:30 PM, Greg KH <gregkh@suse.de> wrote:
>
> On Thu, Apr 10, 2008 at 06:14:55PM +0200, Bert Wesarg wrote:
> > On Thu, Apr 10, 2008 at 2:10 PM, Paul Jackson <pj@sgi.com> wrote:
> > > Bert wrote:
> > > > Btw, I think you can now push for a deprecation of the 'old' mask
> > > > attributes, with the justification you have given above. The other
> > > > possibility is to change sysfs to provide bigger attribute buffers
> > > > (CCed Greg for this).
> > >
> > > On the other hand, and my main point of this message, I can't
> > > see deprecating the mask format files on account of this sort
> > > of analysis.
> > >
> > My statement from above doesn't reflect my opinion. I'm still in
> > flavor with the mask output. And from this discussion, I found a new
> > point for the mask output: its bounded ;-)
> >
> > I just wanted to note, that these new list attributes would be the
> > only way to 'change' the api, ie. introduce a new api and deprecate
> > the old one, and not change the format of the present api.
> >
> > Unfortunately, to support the mask attributes beyond 4k cpus, sysfs
> > has to support greater attribute buffers.
>
> Well, it does already today, you just have to work at it :)
>
> What we can do for these types of files, is to use the "binary
> attribute" file format. With that, you get full control over the buffer
> size and other operations.
>
> So someone should just wrap up the cpu mask sysfs file usage in a
> function that uses the binary attribute instead. Then everyone who uses
> the cpu mask in a sysfs file can use that function instead.
>
> Sound reasonable?
Very. Thanks.
Bert
>
> thanks,
>
> greg k-h
>
prev parent reply other threads:[~2008-04-10 17:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 18:43 Mike Travis
2008-04-08 18:43 ` [PATCH 1/3] x86: modify show_shared_cpu_map in intel_cacheinfo v3 Mike Travis
2008-04-08 19:36 ` Bert Wesarg
2008-04-08 20:44 ` Mike Travis
2008-04-10 14:03 ` Paul Jackson
2008-04-10 17:24 ` Bert Wesarg
2008-04-10 17:36 ` Paul Jackson
2008-04-10 13:57 ` Paul Jackson
2008-04-08 18:43 ` [PATCH 2/3] cpumask: use new cpus_scnprintf function v3 Mike Travis
2008-04-08 19:40 ` Bert Wesarg
2008-04-08 20:46 ` Mike Travis
2008-04-09 15:53 ` Bert Wesarg
2008-04-10 12:49 ` Paul Jackson
2008-04-10 0:32 ` Paul Jackson
2008-04-10 12:13 ` Paul Jackson
2008-04-10 14:05 ` Paul Jackson
2008-04-08 18:43 ` [PATCH 3/3] cpumask: add show cpu map functions v2 Mike Travis
2008-04-08 19:32 ` Bert Wesarg
2008-04-08 20:52 ` Mike Travis
2008-04-09 17:39 ` Bert Wesarg
2008-04-10 0:29 ` Paul Jackson
2008-04-10 6:05 ` Bert Wesarg
2008-04-10 14:13 ` Paul Jackson
2008-04-08 19:33 ` [PATCH 0/3] x86: add cpus_scnprintf function v3 Bert Wesarg
2008-04-08 20:54 ` Mike Travis
2008-04-10 15:03 ` Paul Jackson
2008-04-09 15:11 ` Ingo Molnar
2008-04-09 17:51 ` Bert Wesarg
2008-04-09 20:39 ` Greg KH
2008-04-09 20:52 ` Bert Wesarg
2008-04-09 21:14 ` Greg KH
2008-04-09 21:21 ` Bert Wesarg
2008-04-09 20:59 ` Mike Travis
2008-04-09 21:02 ` Bert Wesarg
2008-04-09 21:15 ` Greg KH
2008-04-10 0:18 ` Paul Jackson
2008-04-10 12:10 ` Paul Jackson
2008-04-10 16:14 ` Bert Wesarg
2008-04-10 16:27 ` Paul Jackson
2008-04-10 17:30 ` Greg KH
2008-04-10 17:36 ` Bert Wesarg [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=36ca99e90804101036o407dda7dyc303bd87f46c5cfc@mail.gmail.com \
--to=bert.wesarg@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.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
Powered by JetHome