[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B45994.7010805@opengridcomputing.com>
Date: Thu, 14 Feb 2008 09:09:08 -0600
From: Steve Wise <swise@...ngridcomputing.com>
To: Felix Marti <felix@...lsio.com>
CC: Roland Dreier <rdreier@...co.com>,
Christoph Lameter <clameter@....com>,
Rik van Riel <riel@...hat.com>, steiner@....com,
Andrea Arcangeli <andrea@...ranet.com>, a.p.zijlstra@...llo.nl,
izike@...ranet.com, linux-kernel@...r.kernel.org, avi@...ranet.com,
linux-mm@...ck.org, daniel.blueman@...drics.com,
Robin Holt <holt@....com>, general@...ts.openfabrics.org,
Andrew Morton <akpm@...ux-foundation.org>,
kvm-devel@...ts.sourceforge.net
Subject: Re: [ofa-general] Re: Demand paging for memory regions
Felix Marti wrote:
>
> That is correct, not a change we can make for T3. We could, in theory,
> deal with changing mappings though. The change would need to be
> synchronized though: the VM would need to tell us which mapping were
> about to change and the driver would then need to disable DMA to/from
> it, do the change and resume DMA.
>
Note that for T3, this involves suspending _all_ rdma connections that
are in the same PD as the MR being remapped. This is because the driver
doesn't know who the application advertised the rkey/stag to. So
without that knowledge, all connections that _might_ rdma into the MR
must be suspended. If the MR was only setup for local access, then the
driver could track the connections with references to the MR and only
quiesce those connections.
Point being, it will stop probably all connections that an application
is using (assuming the application uses a single PD).
Steve.
--
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