lkml.org 
[lkml]   [2009]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [ofa-general] Re: [GIT PULL] please pull ummunotify
On Tue 2009-09-15 07:57:56, Roland Dreier wrote:
>
> > I don't remember seeing discussion of this on lkml. Yes it is in
> > -next...
>
> eg http://lkml.org/lkml/2009/7/31/197 and followups, or search for v2
> and earlier patches.

Well... it seems little overspecialized. Just modifying libc to
provide hooks you want looks like better solution.

> > Basically it allows app to 'trace itself'? ...with interesting mmap()
> > interface, exporting int to userspace, hoping it behaves atomically...?
>
> Yes, it allows app to trace what the kernel does to memory mappings. I
> don't believe there's any real issue to atomicity of mmap'ed memory,
> since userspace really just tests whether read value is == to old read
> value or not.

That still needs memory barriers etc.. to ensure reliable operation,
no?
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


\
 
 \ /
  Last update: 2009-09-28 22:51    [W:0.586 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site