From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by dpdk.org (Postfix) with ESMTP id 21D8E2BB9; Fri, 16 Jun 2017 10:26:41 +0200 (CEST) Received: by mail-qt0-f179.google.com with SMTP id u19so53591697qta.3; Fri, 16 Jun 2017 01:26:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=FI234WGQxWiY/9vyx3NON08S9eUapit9wDf4M22UAxc=; b=DSxYM94ZwyffzgmBrQ8ilzA5/n+qK0RFIZtVS6xkRaMp7ojcS+sYRVaavujVrxHTuD wOkHIiAPY4cyZMVLcLdGT2b/2hOMttBL+xFCKOa3hAuHzEh43yKOY6GovD5GBaSgJuwr nyx7vvAl15ynGPLni5ckRoWY9tYHDzwQhbhRZVFI+CsKBSRc8cMNJBnIVsIOL6R0swk8 l2EdmtM0t/x6wJLnZlN5EvKqO3RyNwULM/ifrqcF3TgewmUihPbczH/3uKT3iExi3320 8+9fzFCdx0cjCRrAp2xneCbjVVh4yGfHQw6nQQSUezTO7Q3HcBHuMoll+wGLflV6/12F LtUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=FI234WGQxWiY/9vyx3NON08S9eUapit9wDf4M22UAxc=; b=nD7IdBeaflfI7c9B27qcqsE76cXBXfO6wvGJTM7zXU1ka2EhM/g6glZOc8V9tLbquP Aa7LQKG6+PhI4GdULQL+7cYK/278rIhki7P+9an+zhvXQl2emTP5B7oiBefDGxoIOO9H UENLYlVOKQ7ZWwjqHvjQT4loXU3WeCmmQ3/PliwXNyVEokIcAj7JKJdYcUpcnz5nk3sC ibe7PqU9DElVxKYd1eIwaPUy3T/2BMipsTwkrsl9xDSDuW4urkVUUfr8nhYRs7Er+7N1 w+KzkEjEaN4K3kvL8SHTIYw+llHpOFeV/pzztU/6L0lzTGu/wTEqI67Hdi9FbcixU2bq 1GqQ== X-Gm-Message-State: AKS2vOy4mrfqIgVC/Cn9FsPiQVH84h3Oa0Hqh6t2zOOKRwr7r7Pldess nI9XMTpyanWfwAkmNAdSF53HovYZxe2B X-Received: by 10.55.72.198 with SMTP id v189mr10618701qka.133.1497601601119; Fri, 16 Jun 2017 01:26:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.90.72 with HTTP; Fri, 16 Jun 2017 01:26:40 -0700 (PDT) In-Reply-To: References: From: Sam Date: Fri, 16 Jun 2017 16:26:40 +0800 Message-ID: To: dev@dpdk.org, users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [DPDK-memory] how qemu waste such long time under dpdk huge page envriment? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jun 2017 08:26:42 -0000 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 : > 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~ >