From: "J.E.J. Bottomley" <James.Bottomley@steeleye.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: James.Bottomley@SteelEye.com, andmike@us.ibm.com, greg@kroah.com,
hch@lst.de, linux-kernel@vger.kernel.org, mochel@osdl.org,
parisc-linux@lists.parisc-linux.org, willy@debian.org
Subject: Re: [parisc-linux] Untested port of parisc_device to generic device interface
Date: Sat, 09 Nov 2002 21:01:29 -0500 [thread overview]
Message-ID: <200211100201.gAA21Uv04824@localhost.localdomain> (raw)
In-Reply-To: Message from "Adam J. Richter" <adam@yggdrasil.com> of "Sat, 09 Nov 2002 16:23:59 PST." <200211100023.QAA27139@baldur.yggdrasil.com>
adam@yggdrasil.com said:
>
> I'd like to know more about what these machines look like in the real
> world. Specifically, I am interested in the trade-off of having a
> parameter to wback_fake_consistent so that it could be enabled or
> disabled on an individual basis.
Actually, so would I. I can suspect why there might exist machines like this
(say the consistent attribute is settable at the pgd level)
> I suspect that the parameter is not worth the clutter because these
> "partially consistent" machines either have a large amount of
> consistent memory, so the case of the allocation failing in the is not
> worth supporting, or it is easy to check for consistent memory on them
> with something like "if ((unsigned long) vaddr < 0xwhatever)", but I'm
> just guessing.
Well, if it has to be done, it can be done by making alloc_consistent return a
handle rather than an address and making wback/invalidate take the handle (but
it's certainly not ideal).
James
next prev parent reply other threads:[~2002-11-10 1:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 0:23 [parisc-linux] Untested port of parisc_device to generic device interface Adam J. Richter
2002-11-10 2:01 ` J.E.J. Bottomley [this message]
2002-11-10 2:15 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2002-11-10 5:20 Adam J. Richter
2002-11-10 1:50 Adam J. Richter
2002-11-09 12:22 Adam J. Richter
2002-11-09 4:51 Adam J. Richter
2002-11-09 5:21 ` Matthew Wilcox
2002-11-09 6:03 ` Greg KH
2002-11-09 15:33 ` J.E.J. Bottomley
2002-11-13 6:13 ` Greg KH
2002-11-13 7:46 ` Miles Bader
2002-11-13 7:52 ` Greg KH
2002-11-13 8:02 ` Miles Bader
2002-11-13 8:10 ` Greg KH
2002-11-13 8:26 ` Miles Bader
2002-11-13 8:25 ` Greg KH
2002-11-13 9:05 ` Miles Bader
[not found] ` <miles@lsi.nec.co.jp>
2002-11-13 20:13 ` Grant Grundler
2002-11-13 20:21 ` J.E.J. Bottomley
2002-11-13 20:37 ` Grant Grundler
2002-11-13 11:59 ` Ivan Kokshaysky
2002-11-13 12:36 ` Marc Zyngier
2002-11-13 16:32 ` Bjorn Helgaas
2002-11-13 17:23 ` J.E.J. Bottomley
2002-11-13 20:33 ` Grant Grundler
2002-11-13 20:44 ` J.E.J. Bottomley
2002-11-13 21:42 ` Grant Grundler
2002-11-13 20:12 ` Grant Grundler
2002-11-09 7:58 ` Marc Zyngier
2002-11-09 18:04 ` Grant Grundler
[not found] <200211090128.RAA31693@adam.yggdrasil.com>
2002-11-09 3:37 ` Matthew Wilcox
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=200211100201.gAA21Uv04824@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=adam@yggdrasil.com \
--cc=andmike@us.ibm.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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).