[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091012202046.GA7648@elte.hu>
Date: Mon, 12 Oct 2009 22:20:46 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Cc: Pavel Machek <pavel@....cz>, Roland Dreier <rdreier@...co.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
Paul Mackerras <paulus@...ba.org>,
Anton Blanchard <anton@...ba.org>,
general@...ts.openfabrics.org, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, Jeff Squyres <jsquyres@...co.com>
Subject: Re: [ofa-general] Re: [GIT PULL] please pull ummunotify
* Jason Gunthorpe <jgunthorpe@...idianresearch.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.
Is that loss of information more acceptable than the loss of information
via the loss of events?
It might be more acceptable because the flag-hint mechanism can at most
cause over-flushing - while with perf events we might miss to invalidate
a range altogether.
Ingo
--
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