DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-dev] [DPDK-memory] how qemu waste such long time under dpdk huge page envriment?
Date: Fri, 16 Jun 2017 16:26:40 +0800	[thread overview]
Message-ID: <CAOE=1Z2RHASPyFPCz2CaW9SSB1dLB_jZWr==ANA+Qmx-c6ARtQ@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z2Dtzt7xsiE=XR=MShSHwb6Z-=JnHdtvRr2MwQpFhpuiQ@mail.gmail.com>

BTW, while running ovs-dpdk, this log is also take long time, does that
mean dpdk request large memory take long time?

EAL: Setting up physically contiguous memory...


2017-06-16 16:11 GMT+08:00 Sam <batmanustc@gmail.com>:

> Hi all,
>
> I'm running `QEMU_CMD ...` to create a vm under dpdk huge page envriment
> (which set huge page 1G). And I enable all events in qemu.
>
> For qemu and ovs-dpdk(ovs-2.4.9 with dpdk-2.2.0) environment, detail log
> is:
>
> > 30012@1497443246.678304:object_dynamic_cast_assert
> qemu:memory-region->qemu:memory-region (/home/hu
> > anghuai/cloud/contrib/qemu-2.6.0/memory.c:1076:memory_region_initfn)
> > 30012@1497443256.274866:object_dynamic_cast_assert
> qio-channel-socket->qio-channel-socket (io/chann
> > el-socket.c:389:qio_channel_socket_init)
>
>
> I don't know why qemu doing 'memory_region_initfn' function in this 10
> second, does anyone know this?
>
> static void memory_region_initfn(Object *obj)
>> {
>>     MemoryRegion *mr = MEMORY_REGION(obj);
>>     ObjectProperty *op;
>>     mr->ops = &unassigned_mem_ops;
>>     mr->enabled = true;
>>     mr->romd_mode = true;
>>     mr->global_locking = true;
>>     mr->destructor = memory_region_destructor_none;
>>     QTAILQ_INIT(&mr->subregions);
>>     QTAILQ_INIT(&mr->coalesced);
>>     op = object_property_add(OBJECT(mr), "container",
>>                              "link<" TYPE_MEMORY_REGION ">",
>>                              memory_region_get_container,
>>                              NULL, /* memory_region_set_container */
>>                              NULL, NULL, &error_abort);
>>     op->resolve = memory_region_resolve_container;
>>     object_property_add(OBJECT(mr), "addr", "uint64",
>>                         memory_region_get_addr,
>>                         NULL, /* memory_region_set_addr */
>>                         NULL, NULL, &error_abort);
>>     object_property_add(OBJECT(mr), "priority", "uint32",
>>                         memory_region_get_priority,
>>                         NULL, /* memory_region_set_priority */
>>                         NULL, NULL, &error_abort);
>>     object_property_add_bool(OBJECT(mr), "may-overlap",
>>                              memory_region_get_may_overlap,
>>                              NULL, /* memory_region_set_may_overlap */
>>                              &error_abort);
>>     object_property_add(OBJECT(mr), "size", "uint64",
>>                         memory_region_get_size,
>>                         NULL, /* memory_region_set_size, */
>>                         NULL, NULL, &error_abort);
>> }
>
>
> Thank you~
>

  reply	other threads:[~2017-06-16  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  8:11 Sam
2017-06-16  8:26 ` Sam [this message]
2017-06-16  8:59   ` Bruce Richardson
2017-06-19  3:12     ` Sam
2017-06-19  3:13       ` Sam

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='CAOE=1Z2RHASPyFPCz2CaW9SSB1dLB_jZWr==ANA+Qmx-c6ARtQ@mail.gmail.com' \
    --to=batmanustc@gmail.com \
    --cc=dev@dpdk.org \
    --cc=users@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).