From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33629)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WuEJi-0003ti-0D
	for qemu-devel@nongnu.org; Tue, 10 Jun 2014 01:09:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WuEJa-0005Kv-S9
	for qemu-devel@nongnu.org; Tue, 10 Jun 2014 01:09:49 -0400
Received: from mx3-phx2.redhat.com ([209.132.183.24]:34059)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1WuEJa-0005K4-KQ
	for qemu-devel@nongnu.org; Tue, 10 Jun 2014 01:09:42 -0400
Date: Tue, 10 Jun 2014 01:09:32 -0400 (EDT)
From: Paolo Bonzini <pbonzini@redhat.com>
Message-ID: <480968011.20454430.1402376972892.JavaMail.zimbra@redhat.com>
In-Reply-To: <20140610020021.GD29724@G08FNSTD100614.fnst.cn.fujitsu.com>
References: <cover.1402299637.git.hutao@cn.fujitsu.com>
	<988dc97c3b3e3c89066b3b3dc8c17b3fccc3c816.1402299637.git.hutao@cn.fujitsu.com>
	<20140609133246.286d749c@thinkpad>
	<20140610020021.GD29724@G08FNSTD100614.fnst.cn.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v4 18/29] hostmem: add file-based
	HostMemoryBackend
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: Hu Tao <hutao@cn.fujitsu.com>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>, Igor Mammedov <imammedo@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>


> > > +#define TYPE_MEMORY_BACKEND_FILE "memory-backend-file"
> > how about naming it after what it really is? "memory-backend-hugepage"
> > Later we could split it into generic superclass mmap-ed
> > "memory-backend-file" and have TPH specific code moved into this backend.
> 
> OK.

Actually I don't think there's anything hugepage-specific in this backend
(except perhaps passing a path instead of a filename).  It could be used
with a tmpfs backing storage like /dev/shm.

Paolo