Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261308AbVDVSNK (ORCPT ); Fri, 22 Apr 2005 14:13:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262102AbVDVSNK (ORCPT ); Fri, 22 Apr 2005 14:13:10 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:60109 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S261308AbVDVSNF (ORCPT ); Fri, 22 Apr 2005 14:13:05 -0400 Subject: Re: [PATCH][RFC][0/4] InfiniBand userspace verbs implementation From: Arjan van de Ven To: Timur Tabi Cc: Roland Dreier , Troy Benjegerdes , linux-kernel@vger.kernel.org, openib-general@openib.org In-Reply-To: <42693A8A.80105@ammasso.com> References: <200544159.Ahk9l0puXy39U6u6@topspin.com> <20050411142213.GC26127@kalmia.hozed.org> <52mzs51g5g.fsf@topspin.com> <4263DBBF.9040801@ammasso.com> <1113840973.6274.84.camel@laptopd505.fenrus.org> <42693A8A.80105@ammasso.com> Content-Type: text/plain Date: Fri, 22 Apr 2005 20:12:58 +0200 Message-Id: <1114193579.10355.38.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-Spam-Score: 3.7 (+++) X-Spam-Report: SpamAssassin version 2.63 on pentafluge.infradead.org summary: Content analysis details: (3.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.1 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org [] 2.5 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address [80.57.133.107 listed in dnsbl.sorbs.net] 0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS [80.57.133.107 listed in dnsbl.sorbs.net] X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1468 Lines: 41 On Fri, 2005-04-22 at 12:55 -0500, Timur Tabi wrote: > Arjan van de Ven wrote: > > On Mon, 2005-04-18 at 11:09 -0500, Timur Tabi wrote: > > > >>Roland Dreier wrote: > >> > >>> Troy> How is memory pinning handled? (I haven't had time to read > >>> Troy> all the code, so please excuse my ignorance of something > >>> Troy> obvious). > >>> > >>>The userspace library calls mlock() and then the kernel does > >>>get_user_pages(). > >> > >>Why do you call mlock() and get_user_pages()? In our code, we only call mlock(), and the > >>memory is pinned. > > > > > > this is a myth; linux is free to move the page about in physical memory > > even if it's mlock()ed!! > > Can you tell me when Linux actually does this? I know in theory it can happen, but I've > never seen it. Does the code to implement moving of data from one physical page to > another even exist in any version of Linux? hot(un)plug memory. > > Also, what would be the point? What reason would there be to move some data from one > physical page to another, while keeping the same virtual address? so that you can hot unplug the dimm in question. I guess that's a bit of a high end though though... so maybe you don't care about it. - 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/