lkml.org 
[lkml]   [2009]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [ofa-general] Re: [GIT PULL] please pull ummunotify
Ingo Molnar wrote:
> * Jason Gunthorpe <jgunthorpe@obsidianresearch.com> wrote:
>
>
>> On Mon, Oct 12, 2009 at 08:19:44PM +0200, Ingo Molnar wrote:
>>
>>
>>>> After that point the scheme is perfectly lossless.
>>>>
>>> Well if it can OOM it's not lossless, obviously. You just define
>>> "event loss" to be equivalent to "Destruction of the universe." ;-)
>>>
>> It can't OOM once the ummunotify registration is done - when an event
>> occurs it doesn't allocate any memory and it doesn't loose events.
>>
>
> Well, it has built-in event loss via the UMMUNOTIFY_FLAG_HINT mechanism:
> any double events on the same range will cause an imprecise event to be
> recorded and cause the loss of information.
>

The target (MPI) application doesn't care about how many events are
coming here. It just needs to know whether something has been
invalidated in the range. If so, it destroy the whole RDMA window
anyway. So it's actually _good_ that multiple events are merged into a
single one: the application only has to process a single event per
partially-invalidated range.

Brice



\
 
 \ /
  Last update: 2009-10-13 07:47    [W:0.148 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site