From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Roland Dreier <roland@kernel.org>,
qemu-devel@nongnu.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Sean Hefty <sean.hefty@intel.com>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag
Date: Tue, 09 Apr 2013 13:56:00 -0400 [thread overview]
Message-ID: <51645630.3030608@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130409163929.GA7661@redhat.com>
On 04/09/2013 12:39 PM, Michael S. Tsirkin wrote:
> 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?
>
It's killed by cgroups - not a CPU exception.
The same test works fine using TCP migration with cgroups - everything
is fine there.
The memory that RDMA attempted to register hits some kind of cgroups policy
which results in a kernel message saying that the cgroup swap limit was hit
and then it goes ahead and kills the process altogether.
It's not a QEMU problem - it seems to be a kernel bug.
next prev parent reply other threads:[~2013-04-09 17:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 15:51 [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag Michael S. Tsirkin
2013-04-02 15:51 ` Michael S. Tsirkin
2013-04-02 16:57 ` Roland Dreier
2013-04-02 17:05 ` Michael S. Tsirkin
2013-04-02 22:17 ` Michael R. Hines
2013-04-03 16:07 ` Michael S. Tsirkin
2013-04-05 20:17 ` Michael R. Hines
2013-04-05 20:43 ` Roland Dreier
2013-04-05 20:51 ` Michael R. Hines
2013-04-05 21:03 ` Roland Dreier
2013-04-05 21:32 ` Michael R. Hines
2013-04-09 19:03 ` Michael S. Tsirkin
2013-04-10 1:26 ` Michael R. Hines
2013-04-10 3:24 ` Michael S. Tsirkin
2013-04-10 4:32 ` Michael R. Hines
2013-04-10 5:32 ` Michael S. Tsirkin
[not found] ` <516589C8.1040606@linux.vnet.ibm.com>
2013-04-10 15:05 ` Michael S. Tsirkin
2013-04-10 16:28 ` Michael R. Hines
2013-04-09 19:09 ` Michael S. Tsirkin
2013-04-05 20:54 ` Michael R. Hines
2013-04-09 16:39 ` Michael S. Tsirkin
2013-04-09 17:56 ` Michael R. Hines [this message]
2013-04-09 19:00 ` Michael S. Tsirkin
2013-04-09 19:12 ` Michael S. Tsirkin
2013-04-09 20:34 ` Michael S. Tsirkin
2013-04-09 20:37 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51645630.3030608@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox