[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080226072137.GD26611@minantech.com>
Date: Tue, 26 Feb 2008 09:21:37 +0200
From: glebn@...taire.com (Gleb Natapov)
To: Nick Piggin <nickpiggin@...oo.com.au>
Cc: Robin Holt <holt@....com>, steiner@....com,
Andrea Arcangeli <andrea@...ranet.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-mm@...ck.org,
Izik Eidus <izike@...ranet.com>,
Kanoj Sarcar <kanojsarcar@...oo.com>,
Roland Dreier <rdreier@...co.com>,
linux-kernel@...r.kernel.org, Avi Kivity <avi@...ranet.com>,
kvm-devel@...ts.sourceforge.net, daniel.blueman@...drics.com,
general@...ts.openfabrics.org, akpm@...ux-foundation.org,
Christoph Lameter <clameter@....com>
Subject: Re: [ofa-general] Re: [patch 5/6] mmu_notifier: Support for
drivers with revers maps (f.e. for XPmem)
On Tue, Feb 26, 2008 at 05:11:32PM +1100, Nick Piggin wrote:
> > You are missing one point here. The MPI specifications that have
> > been out there for decades do not require the process use a library
> > for allocating the buffer. I realize that is a horrible shortcoming,
> > but that is the world we live in. Even if we could change that spec,
>
> Can you change the spec?
Not really. It will break all existing codes. MPI-2 provides a call for
memory allocation (and it's beneficial to use this call for some interconnects),
but many (most?) applications are still written for MPI-1 and those that
are written for MPI-2 mostly uses the old habit of allocating memory by malloc(),
or even use stack or BSS memory for communication buffer purposes.
--
Gleb.
--
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