From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:43640)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UHyGD-0000PP-W8
	for qemu-devel@nongnu.org; Tue, 19 Mar 2013 11:15:40 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UHyGB-0006Ed-8j
	for qemu-devel@nongnu.org; Tue, 19 Mar 2013 11:15:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:62609)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mst@redhat.com>) id 1UHyGB-0006EL-27
	for qemu-devel@nongnu.org; Tue, 19 Mar 2013 11:15:31 -0400
Date: Tue, 19 Mar 2013 17:16:07 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20130319151606.GA13649@redhat.com>
References: <1363576743-6146-1-git-send-email-mrhines@linux.vnet.ibm.com>
	<1363576743-6146-4-git-send-email-mrhines@linux.vnet.ibm.com>
	<20130318104013.GE5267@redhat.com>
	<5147780C.1080800@linux.vnet.ibm.com>
	<20130318212646.GB20406@redhat.com>
	<5147A209.80202@linux.vnet.ibm.com>
	<20130319081939.GC11259@redhat.com>
	<51487F68.2060305@linux.vnet.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51487F68.2060305@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH RDMA support v4: 03/10] more verbose
 documentation of the RDMA transport
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com, pbonzini@redhat.com

On Tue, Mar 19, 2013 at 11:08:24AM -0400, Michael R. Hines wrote:
> This is actual a much bigger problem that I thought, not just for RDMA:
> 
> Currently the *sender* side is does not support overcommit
> during a regular TCP migration.......I assume because the
> migration_bitmap does not know which memory is mapped or
> unmapped by the host kernel.
> 
> Is this a known issue?
> 
> - Michael

I don't really understand what you are saying here.
Do you see some bug with migration where we might use
more memory than allowed by cgroups?