All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: haifeng.lin@huawei.com, jerry.lilijun@huawei.com,
	n.nikolaev@virtualopensystems.com, qemu-devel@nongnu.org,
	milo.raofei@huawei.com, arei.gonglei@huawei.com
Subject: Re: [Qemu-devel] [PATCH v1] vhost-user: fix not send all hugepage files to vhost-user
Date: Wed, 04 Feb 2015 15:02:19 +0100	[thread overview]
Message-ID: <54D2266B.5050305@redhat.com> (raw)
In-Reply-To: <20150204135200.GA16345@redhat.com>



On 04/02/2015 14:52, Michael S. Tsirkin wrote:
> I'm not sure: does memory core ever give us two adjacent
> RAM segments that we *can* merge?

I don't think so.  Memory core merges ranges already if the following holds:

- same memory region
- same dirty logging mode
- same readonly behavior (ignore reads, trap reads as MMIO, read/write)
- r2 end address is the same as r1 start address
- r2's offset in the memory region is equal to r1's plus the size of r1

Paolo

> If yes it would trigger, and extra memory slots slow down lookups
> linearly so they aren't free.

  reply	other threads:[~2015-02-04 14:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  6:02 [Qemu-devel] [PATCH v1] vhost-user: fix not send all hugepage files to vhost-user haifeng.lin
2014-12-18  5:06 ` Linhaifeng
2015-01-29  3:58   ` Linhaifeng
2015-01-29 10:51     ` Michael S. Tsirkin
2015-01-29 13:02       ` Linhaifeng
2015-02-01 23:29 ` Paolo Bonzini
2015-02-03 13:09   ` Linhaifeng
2015-02-04 13:52   ` Michael S. Tsirkin
2015-02-04 14:02     ` Paolo Bonzini [this message]
2015-02-15 12:07   ` Linhaifeng

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=54D2266B.5050305@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=haifeng.lin@huawei.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=milo.raofei@huawei.com \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.