All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Lynch <ntl@pobox.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH/RFC] sysfs cache code rewrite
Date: Wed, 07 Jan 2009 17:51:42 +1100	[thread overview]
Message-ID: <1231311102.14860.80.camel@pasglop> (raw)
In-Reply-To: <20090106212533.GB7376@localdomain>

On Tue, 2009-01-06 at 15:25 -0600, Nathan Lynch wrote:
> Please unsubscribe me from... wait, that's not what I meant to say.
> 
> Any thoughts or questions on this one?  I posted this right before the
> holidays so my feelings aren't hurt by the lack of response (yet!)
> 
> To summarize why I think this should go in 2.6.29:
> - Userspace will now be able to determine the true cache topology
>   (the current code doesn't tell you which caches are shared between
>   CPUs).
> - More complete information will be presented on systems that use
>   [di]-cache-block-size properties instead of [di]-cache-line-size. 
> - While overall LOC has increased, the documentation is better, and the
>   functions are much shorter and less complex.

I'm pretty happy about it. However, it fails build when merged on top of
linus current upstream due to some cpumask changes.

I don't know quite the detail of the new cpumask stuff ... It could be
as simple as passing a pointer instead of the value in the
cpumask_scnprintf call though...

Can you check and produce a new patch pls ?

Cheers,
Ben.

  reply	other threads:[~2009-01-07  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-24  4:55 [PATCH/RFC] sysfs cache code rewrite Nathan Lynch
2009-01-06 21:25 ` Nathan Lynch
2009-01-07  6:51   ` Benjamin Herrenschmidt [this message]
2009-01-07  6:55     ` Benjamin Herrenschmidt
2009-01-07  9:46       ` Nathan Lynch
2009-01-07 10:15         ` Benjamin Herrenschmidt
2009-01-07 18:48           ` Nathan Lynch

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=1231311102.14860.80.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ntl@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.