Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758958AbZJMGjS (ORCPT ); Tue, 13 Oct 2009 02:39:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758851AbZJMGjR (ORCPT ); Tue, 13 Oct 2009 02:39:17 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:46065 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758813AbZJMGjQ (ORCPT ); Tue, 13 Oct 2009 02:39:16 -0400 Date: Tue, 13 Oct 2009 08:38:16 +0200 From: Ingo Molnar To: Brice Goglin Cc: Jason Gunthorpe , Pavel Machek , Roland Dreier , Peter Zijlstra , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, Paul Mackerras , Anton Blanchard , general@lists.openfabrics.org, akpm@linux-foundation.org, torvalds@linux-foundation.org, Jeff Squyres Subject: Re: [ofa-general] Re: [GIT PULL] please pull ummunotify Message-ID: <20091013063816.GB9470@elte.hu> References: <1253198976.14935.27.camel@laptop> <20090929171332.GD14405@elf.ucw.cz> <20090930094456.GD24621@elte.hu> <20090930160232.GZ22310@obsidianresearch.com> <20091012181944.GF17138@elte.hu> <20091012193048.GA20313@obsidianresearch.com> <20091012202046.GA7648@elte.hu> <4AD41373.8010108@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AD41373.8010108@inria.fr> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2237 Lines: 62 * Brice Goglin wrote: > Ingo Molnar wrote: > > * Jason Gunthorpe 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. it's not unconditionally good as the fuzzy-merge-events rule: events[n].flags = UMMUNOTIFY_EVENT_FLAG_HINT; events[n].hint_start = max(reg->start, reg->hint_start); events[n].hint_end = min(reg->end, reg->hint_end); in essence merges flushes into a single interval - which inevitably might include areas of memory that were not flushed at all. For example these two flushes: [...] [...] Would be merged into: [..................] Btw., isnt the above max/min logic buggy, causing lost events? Shouldnt it be: events[n].hint_start = min(reg->start, reg->hint_start); events[n].hint_end = max(reg->end, reg->hint_end); ? Ingo -- 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/