[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ada7hw0gsqz.fsf@cisco.com>
Date: Tue, 15 Sep 2009 07:57:56 -0700
From: Roland Dreier <rdreier@...co.com>
To: Pavel Machek <pavel@....cz>
Cc: linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
general@...ts.openfabrics.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org
Subject: Re: [ofa-general] Re: [GIT PULL] please pull ummunotify
> 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.
> 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.
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists