On Tue, 2002-02-12 at 16:48, Russell King wrote:
> On Tue, Feb 12, 2002 at 04:36:34PM +0100, Daniel Stodden wrote:
> > ARM does GFP_KERNEL, and then __ioremaps the underlying pages.
> > ugh. is that the only way to get the area coherent?
> Yes. Cache bits are in the page tables, and it would be idiotic to
> manipulate the cache bits on a 1MB granularity over the kernel
> direct mapped space.
> > furthermore i don't see why this could not be interrupt safe.
> GFP_KERNEL in the page table allocation functions mainly. We've been
> around and around this recently on this mailing list, so I'm not going
> to say anything further. I don't want another long discussion about
> this subject taking my time away from doing real work on ARM. If you're
> really interested in the outcome, please examine the lkml archives.
ok. i read part of the old thread now. sorry. didn't know that this had
already been issued.
so, based on the fact that
1. _most_ archs can easily do atomically.
2. those which don't aren't necessarily the better ones.
3. many drivers may prefer/be able to alloc through during
3.5 some may not.
4. even on arm, __ioremap() takes a gfp for quite some time now=20
and nobody seems to disagree.
then why does pci_alloc_consistent() not just take gfp flags and people
put in what their personal preference is?
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/