[lkml]   [2008]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ofa-general] Re: Demand paging for memory regions
On Thu, 14 Feb 2008, Steve Wise wrote:

> 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).

Right but if the system starts reclaiming pages of the application then we
have a memory shortage. So the user should address that by not running
other apps concurrently. The stopping of all connections is still better
than the VM getting into major trouble. And the stopping of connections in
order to move the process memory into a more advantageous memory location
(f.e. using page migration) or stopping of connections in order to be able
to move the process memory out of a range of failing memory is certainly

 \ /
  Last update: 2008-02-14 20:41    [W:0.125 / U:4.228 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site