linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: USB mass storage and ARM cache coherency
Date: Thu, 11 Mar 2010 21:44:31 +0000	[thread overview]
Message-ID: <1268343871.22204.709.camel@pasglop> (raw)
In-Reply-To: <20100310035249.GB17693@linux-sh.org>

On Wed, 2010-03-10 at 12:52 +0900, Paul Mundt wrote:
> Well, it does start to get a bit painful with sparsemem section or
> NUMA
> node IDs also digging in to the page flags on 32-bit.. the benefits
> would
> have to be pretty compelling to offset the pain. 

Unless we play a dangerous trick and re-use another flag that isn't
meaningful for allocated pages... maybe PG_buddy ? Or do I miss
something about that guy semantics ?

Cheers,
Ben.


      reply	other threads:[~2010-03-11 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100302211049V.fujita.tomonori@lab.ntt.co.jp>
     [not found] ` <1267549527.15401.78.camel@e102109-lin.cambridge.arm.com>
     [not found]   ` <20100303215437.GF2579@ucw.cz>
     [not found]     ` <1267709756.6526.380.camel@e102109-lin.cambridge.arm.com>
     [not found]       ` <20100304135128.GA12191@atrey.karlin.mff.cuni.cz>
     [not found]         ` <1267712512.31654.176.camel@mulgrave.site>
     [not found]           ` <1267716578.6526.483.camel@e102109-lin.cambridge.arm.com>
     [not found]             ` <20100304154103.GA9384@linux-sh.org>
     [not found]               ` <1267726049.6526.543.camel@e102109-lin.cambridge.arm.com>
     [not found]                 ` <1267738660.22204.77.camel@pasglop>
2010-03-05  1:17                   ` USB mass storage and ARM cache coherency Paul Mundt
2010-03-05  4:44                     ` Benjamin Herrenschmidt
2010-03-10  3:52                       ` Paul Mundt
2010-03-11 21:44                         ` Benjamin Herrenschmidt [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=1268343871.22204.709.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).