Hello,

On 02/11/2010 09:34 PM, Miklos Szeredi wrote:
quoted text
> On Thu, 11 Feb 2010, Tejun Heo wrote:
>> It's not like it's something completely foreign.  It's a limitation
>> which can also be found in shared memory and the server side mmap
>> doesn't really have much to do with it.  It's also necessary to avoid
>> aliasing issues among clients.
> 
> What aliasing issues among clients?  That's a job for the arch
> dependent part of mmap.  And as you said, there's not a lot the driver
> can do (except play with ->vm_pgoff) to influence the address
> selection.
>
> And playing with ->vm_pgoff is *not* a valid thing to do for the
> client, at least not on "normal" mmaps.

That's the requirement coming from allowing the server to determine
how these mmaps are served, not from the fact that the management is
done via server side mmaps or the server maps those regions into its
process address space.  No matter how you do it, if you want to mix
and match client mmap requests, the SHMLBA alignment will be visible.
I suppose you're talking about not allowing offsets to be adjusted at
all but I don't think that's a restriction we would want to have at
the kernel API level because offset might encode different things for
device mmaps.

Thanks.

-- 
tejun
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/