test suite reviews and discussions
 help / color / mirror / Atom feed
From: Yong Liu <yong.liu@intel.com>
To: dts@dpdk.org
Subject: [dts] [PATCH] Allocate hugepage from socket 0 for i686 and x86_x32
Date: Fri, 24 Jul 2015 15:18:02 +0800	[thread overview]
Message-ID: <1437722282-7874-1-git-send-email-yong.liu@intel.com> (raw)

From: Marvin Liu <yong.liu@intel.com>

dts will allocate 512*2M hugepages for 32bit validation. If seperated on two
sockets, hugepage on one socket may not enough for some applictation.

Add timeout for waiting interface ipv6 ready.

Signed-off-by: Marvin Liu <yong.liu@intel.com>

diff --git a/framework/dut.py b/framework/dut.py
index 722b8a7..f93d696 100644
--- a/framework/dut.py
+++ b/framework/dut.py
@@ -271,7 +271,12 @@ class Dut(Crb):
                 arch_huge_pages = hugepages if hugepages > 0 else 256
 
             if total_huge_pages != arch_huge_pages:
-                self.set_huge_pages(arch_huge_pages)
+                # for i686 and x86_x32 just use hugepage from socket 0
+                if hugepages != 4096:
+                    self.set_huge_pages(arch_huge_pages, numa=0)
+                    print dts.GREEN("Hugepage allocated from socket 0, please take care!!!")
+                else:
+                    self.set_huge_pages(arch_huge_pages)
 
         self.mount_huge_pages()
         self.hugepage_path = self.strip_hugepage_path()
@@ -871,6 +876,8 @@ class Dut(Crb):
             if self.tester.ports_info[tester_port]['type'] != 'ixia':
                 port = self.tester.ports_info[tester_port]['port']
                 port.enable_ipv6()
+        # sleep a while for ipv6 ready
+        time.sleep(1)
 
     def check_port_occupied(self, port):
         out = self.alt_session.send_expect('lsof -i:%d' % port, '# ')
-- 
1.9.3

                 reply	other threads:[~2015-07-24  7:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1437722282-7874-1-git-send-email-yong.liu@intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@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).