Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162927Ab3DEUoO (ORCPT ); Fri, 5 Apr 2013 16:44:14 -0400 Received: from na3sys010aog105.obsmtp.com ([74.125.245.78]:51304 "HELO na3sys010aog105.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1162759Ab3DEUoM (ORCPT ); Fri, 5 Apr 2013 16:44:12 -0400 MIME-Version: 1.0 In-Reply-To: <515F3160.4020007@linux.vnet.ibm.com> References: <20130324155153.GA8597@redhat.com> <515F3160.4020007@linux.vnet.ibm.com> From: Roland Dreier Date: Fri, 5 Apr 2013 13:43:49 -0700 X-Google-Sender-Auth: Efn-6ymzYq19jJCmKWBwTpx_4Nc Message-ID: Subject: Re: [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag To: "Michael R. Hines" Cc: "Michael S. Tsirkin" , Jason Gunthorpe , Sean Hefty , Hal Rosenstock , Yishai Hadas , Christoph Lameter , "linux-rdma@vger.kernel.org" , LKML , qemu-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 743 Lines: 17 On Fri, Apr 5, 2013 at 1:17 PM, Michael R. Hines wrote: > I also removed the IBV_*_WRITE flags on the sender-side and activated > cgroups with the "memory.memsw.limit_in_bytes" activated and the migration > with RDMA also succeeded without any problems (both with *and* without GIFT > also worked). Not sure I'm interpreting this correctly. Are you saying that things worked without actually setting the GIFT flag? In which case why are we adding this flag? - R. -- 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/