On Sun, 06 Aug 2006 10:01:55 -0500
James Bottomley <[email protected]> wrote:
> The simple part of the proposal is to give non-highmem architectures
> access to the kmap API for the purposes of overriding (this is what the
> attached patch does).
>
> The more controversial part of the proposal is that we should now
> require all architectures with coherence issues to manage data coherence
> via the kmap/kunmap API. Thus driver writers never have to write code
> like
kmap() is a nasty thing. It has theoretical deadlock problems (which used
to be real ones back in the 2.4 days) and the present implementation uses a
kernel-wide lock.
We've been gradually and sporadically working to make kmap() go away, so
please let's not do anything which encourages its use.
kmap_atomic() is much preferred. Can this initiative be recast around
kmap_atomic()?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
