[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130409163929.GA7661@redhat.com>
Date: Tue, 9 Apr 2013 19:39:30 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: "Michael R. Hines" <mrhines@...ux.vnet.ibm.com>
Cc: Roland Dreier <roland@...nel.org>, qemu-devel@...gnu.org,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
Yishai Hadas <yishaih@...lanox.com>,
LKML <linux-kernel@...r.kernel.org>,
Hal Rosenstock <hal.rosenstock@...il.com>,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
Sean Hefty <sean.hefty@...el.com>,
Christoph Lameter <cl@...ux.com>
Subject: Re: [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag
On Fri, Apr 05, 2013 at 04:54:39PM -0400, Michael R. Hines wrote:
> To be more specific, here's what I did:
>
> 1. apply kernel module patch - re-insert module
> 1. QEMU does: ibv_reg_mr(........IBV_ACCESS_GIFT | IBV_ACCESS_REMOTE_READ)
> 2. Start the RDMA migration
> 3. Migration completes without any errors
>
> This test does *not* work with a cgroup swap limit, however. The
> process gets killed. (Both with and without GIFT)
>
> - Michael
Try to attach a debugger and see where it is when it gets killed?
> On 04/05/2013 04:43 PM, Roland Dreier wrote:
> >On Fri, Apr 5, 2013 at 1:17 PM, Michael R. Hines
> ><mrhines@...ux.vnet.ibm.com> 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@...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