On Tue, Jan 08, 2008 at 03:49:07AM +0100, Nick Piggin wrote: > On Tue, Jan 08, 2008 at 03:37:46AM +0100, Andi Kleen wrote: > > > - strongly ordered > > > - bufferable only * > > > - device, sharable * > > > - device, unsharable > > > - memory, bufferable and cacheable, write through, no write allocate > > > - memory, bufferable and cacheable, write back, no write allocate > > > - memory, bufferable and cacheable, write back, write allocate > > > - implementation defined combinations (eg, selecting "minicache") > > > - and a set of 16 states to allow the policy of inner and outer levels > > > of cache to be defined (two bits per level). > > > > Do you need all of those in user space? Perhaps you could give > > the bits different meanings depending on user or kernel space. > > I think Nick et.al. just need the bits for user space; they won't > > care about kernel mappings. > > Yes correct -- they are only for userspace mappings. Though that includes mmaps > of /dev/mem and device drivers etc. /dev/mem can be always special cased by checking the VMA flags, can't it? -Andi - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
