From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <emre.eraltan@6wind.com>
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com
 [IPv6:2607:f8b0:4001:c03::22d])
 by dpdk.org (Postfix) with ESMTP id 6940930E
 for <dev@dpdk.org>; Tue, 28 May 2013 05:15:19 +0200 (CEST)
Received: by mail-ie0-f173.google.com with SMTP id k13so369911iea.4
 for <dev@dpdk.org>; Mon, 27 May 2013 20:15:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:x-gm-message-state;
 bh=YKh54kyMbXJVkV6RbOPAAh/l/ycU5QP79FwM5W9qXyM=;
 b=JeJgRu7aQPDu9qU6nVOqSjo6LN6DadP3mkYD4wb9ZF+E5k918PL3M61ybes1xnE1ai
 C3t64lsPhimrsGQ3MgZ2PWcWiok9H8IrAHR7AUhvtyKI1OXyhvVIJLOLPNwAY1U1WgRg
 PCe2hbNJUhuY1DbW/eMQxowwA9k1Kt2G4ykADGUl9PWjY4C1Succ2LeODG5Q49UfrxHu
 X8ziren/DMuUQJFQyhtzOjnF5G9TSa5Z8UwfY0Q1hfP36eEpZzWIdPz9sBrlPY2906Bi
 yO4ejbXx86kRfyasCtO/X0+9T8r9HLjJxkG2l8JEDSm61MC+EZNdk5tiiyRQVodnVS+s
 urMA==
X-Received: by 10.50.112.4 with SMTP id im4mr6229995igb.1.1369710925003;
 Mon, 27 May 2013 20:15:25 -0700 (PDT)
Received: from [172.20.0.144] (50-203-21-194-static.hfc.comcastbusiness.net.
 [50.203.21.194])
 by mx.google.com with ESMTPSA id ij6sm16389822igb.1.2013.05.27.20.15.22
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 27 May 2013 20:15:24 -0700 (PDT)
Message-ID: <51A4214B.8040703@6wind.com>
Date: Mon, 27 May 2013 20:15:23 -0700
From: Emre Eraltan <emre.eraltan@6wind.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Shinae Woo <shinae2012@gmail.com>
References: <CA+f=ZztBO=fTqSvj7n8SwKZUNz=fhOq1LcaFMJGJMRhy7xi41w@mail.gmail.com>
 <20130528113005.5E6D.C42C3789@sakura.ad.jp>
 <CA+f=Zzvyfgu8GcdP4R2W6qi0gfEpDhdEctHnhxmqYuTn8U+n3A@mail.gmail.com>
In-Reply-To: <CA+f=Zzvyfgu8GcdP4R2W6qi0gfEpDhdEctHnhxmqYuTn8U+n3A@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------040303000004080805070607"
X-Gm-Message-State: ALoCoQmrpaF69prv0SMcF0+BceXjVsXrb9BiLhz6OwMKhY/d/hOksVqq2MUB9Wk5W6TmF56K35b/
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Performances are not scale with multiple ports
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 03:15:20 -0000

This is a multi-part message in MIME format.
--------------040303000004080805070607
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello Shinae,

Did you try to use the testpmd tool with multiple queues per port? It 
gives you more flexibility compared to l2fwd app.

You need to trigger the RSS feature of the NIC by sending different 
streams (just by changing the destination port for instance or any 
information in the 5-tuple). This will load balance your packets among 
several cores so that you can probe multiple queues with different 
cores. Otherwise, you will use only one core (or thread if HT is 
enabled) per port for the RX side.

Best Regards,
Emre

-- 
Emre ERALTAN
6WIND Field Application Engineer


On 27/05/2013 20:05, Shinae Woo wrote:
> Thanks for sharing Naoto.
>
> So in your experiments, the forwarding performance still does not 
> reach the line rate.
>
> Your perf record shows that the cpu spend most of the time in polling 
> for receiving packets,
> and no other heavy operation.
> Even though the application polling packets in its best,
> the forwarder miss some packets from elsewhere from the application-side.
>
> The dpdk document shows that 160Mpps forwarding performance in 2 sockets,
> but I can only reach the 13 Mpps in 2 ports.
> Even doubling the number of ports to 4 ports, the performance is still 
> less than 17Mpps.
>
> I want to know where is the bottleneck lies in my environments, or
> how I can reprocuce the same performance as the dpdk published.
>
> Thank you,
> Shinae
>
>
>
> On Tue, May 28, 2013 at 11:30 AM, Naoto MATSUMOTO 
> <n-matsumoto@sakura.ad.jp <mailto:n-matsumoto@sakura.ad.jp>> wrote:
>
>
>     FYI: Disruptive IP Networking with Intel DPDK on Linux
>     http://slidesha.re/SeVFZo
>
>
>     On Tue, 28 May 2013 11:26:30 +0900
>     Shinae Woo <shinae2012@gmail.com <mailto:shinae2012@gmail.com>> wrote:
>
>     > Hello, all.
>     >
>     > I play the dpdk-1.2.3r1 with examples.
>     >
>     > But I can not achieve the line-rate packet receive performance,
>     > and the performance is not scale with multiple ports.
>     >
>     > For example, in example l2fwd, I have tested two cases with 2
>     ports, and 4
>     > ports,
>     > using belowed command line each
>     >
>     > ./build/l2fwd -cf -n3 -- -p3
>     > ./build/l2fwd -cf -n3 -- -pf
>     >
>     > But both cases, the aggregated performance are not scale.
>     >
>     > == experiments environments ==
>     > - Two Intel 82599 NICs (total 4 ports)
>     > - Intel Xeon X5690  @ 3.47GHz * 2 (total 12 cores)
>     > - 1024 * 2MB hugepages
>     > - Linux 2.6.38-15-server
>     > - Each ports receiving 10Gbps of traffic of 64 bytes packets,
>     14.88Mpps.
>     >
>     > *1. Packet forwarding performance*
>     >
>     > In 2 ports case,  receive performance is 13Mpps,
>     > In 4 ports case,  not 26Mbps, only 16.8Mpps.
>     >
>     > Port statistics ====================================
>     > Statistics for port 0 ------------------------------
>     > Packets sent:                  4292256
>     > Packets received:              6517396
>     > Packets dropped:               2224776
>     > Statistics for port 1 ------------------------------
>     > Packets sent:                  4291840
>     > Packets received:              6517044
>     > Packets dropped:               2225556
>     > Aggregate statistics ===============================
>     > Total packets sent:            8584128
>     > Total packets received:       13034472
>     > Total packets dropped:         4450332
>     > ====================================================
>     >
>     > Port statistics ====================================
>     > Statistics for port 0 ------------------------------
>     > Packets sent:                  1784064
>     > Packets received:              2632700
>     > Packets dropped:                848128
>     > Statistics for port 1 ------------------------------
>     > Packets sent:                  1784104
>     > Packets received:              2632196
>     > Packets dropped:                848596
>     > Statistics for port 2 ------------------------------
>     > Packets sent:                  3587616
>     > Packets received:              5816344
>     > Packets dropped:               2200176
>     > Statistics for port 3 ------------------------------
>     > Packets sent:                  3587712
>     > Packets received:              5787848
>     > Packets dropped:               2228684
>     > Aggregate statistics ===============================
>     > Total packets sent:           10743560
>     > Total packets received:       16869152
>     > Total packets dropped:         6125608
>     > ====================================================
>     >
>     > *2. Packet receiving performance*
>     > I fix the codes for only receiving packets (not forwarding),
>     > the performance is still not scalable as each 13.3Mpps, 18Mpps.
>     >
>     > Port statistics ====================================
>     > Statistics for port 0 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              6678860
>     > Packets dropped:                     0
>     > Statistics for port 1 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              6646120
>     > Packets dropped:                     0
>     > Aggregate statistics ===============================
>     > Total packets sent:                  0
>     > Total packets received:       13325012
>     > Total packets dropped:               0
>     > ====================================================
>     >
>     > Port statistics ====================================
>     > Statistics for port 0 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              3129624
>     > Packets dropped:                     0
>     > Statistics for port 1 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              3131292
>     > Packets dropped:                     0
>     > Statistics for port 2 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              6260908
>     > Packets dropped:                     0
>     > Statistics for port 3 ------------------------------
>     > Packets sent:                        0
>     > Packets received:              6238764
>     > Packets dropped:                     0
>     > Aggregate statistics ===============================
>     > Total packets sent:                  0
>     > Total packets received:       18760640
>     > Total packets dropped:               0
>     > ====================================================
>     >
>     > The question is that
>     > 1. How I can achieve each port receiving full 14.88Mpps ?
>     >     What might be the bottleneck in current environment?
>     > 2. Why the performance using multiple ports is not scale?
>     >     I guess doubling ports shows the doubling the receiving
>     performance,
>     >     but it shows not. I am curious about what is limiting the packet
>     > receivng performance.
>     >
>     > Thanks,
>     > Shinae
>
>     --
>     SAKURA Internet Inc. / Senior Researcher
>     Naoto MATSUMOTO <n-matsumoto@sakura.ad.jp
>     <mailto:n-matsumoto@sakura.ad.jp>>
>     SAKURA Internet Research Center <http://research.sakura.ad.jp/>
>
>

--------------040303000004080805070607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hello Shinae,<br>
    <br>
    Did you try to use the testpmd tool with multiple queues per port?
    It gives you more flexibility compared to l2fwd app.<br>
    <br>
    You need to trigger the RSS feature of the NIC by sending different
    streams (just by changing the destination port for instance or any
    information in the 5-tuple). This will load balance your packets
    among several cores so that you can probe multiple queues with
    different cores. Otherwise, you will use only one core (or thread if
    HT is enabled) per port for the RX side.<br>
    <br>
    Best Regards,<br>
    Emre<br>
    <pre class="moz-signature" cols="72">-- 
Emre ERALTAN
6WIND Field Application Engineer
</pre>
    <br>
    <div class="moz-cite-prefix">On 27/05/2013 20:05, Shinae Woo wrote:<br>
    </div>
    <blockquote
cite="mid:CA+f=Zzvyfgu8GcdP4R2W6qi0gfEpDhdEctHnhxmqYuTn8U+n3A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>Thanks for sharing Naoto.<br>
              <br>
            </div>
            So in your experiments, the forwarding performance still
            does not reach the line rate.<br>
          </div>
          <br>
          Your perf record shows that the cpu spend most of the time in
          polling for receiving packets, <br>
        </div>
        <div>and no other heavy operation.<br>
        </div>
        <div>Even though the application polling packets in its best,<br>
          the forwarder miss some packets from elsewhere from the
          application-side.<br>
          <br>
        </div>
        <div>The dpdk document shows that 160Mpps forwarding performance
          in 2 sockets,<br>
        </div>
        <div>but I can only reach the 13 Mpps in 2 ports. <br>
          Even doubling the number of ports to 4 ports, the performance
          is still less than 17Mpps.<br>
          <br>
        </div>
        <div>I want to know where is the bottleneck lies in my
          environments, or<br>
        </div>
        <div>how I can reprocuce the same performance as the dpdk
          published.<br>
          <br>
        </div>
        <div>Thank you,<br>
        </div>
        <div>Shinae<br>
        </div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Tue, May 28, 2013 at 11:30 AM, Naoto
          MATSUMOTO <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:n-matsumoto@sakura.ad.jp" target="_blank">n-matsumoto@sakura.ad.jp</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
            FYI: Disruptive IP Networking with Intel DPDK on Linux<br>
            <a moz-do-not-send="true" href="http://slidesha.re/SeVFZo"
              target="_blank">http://slidesha.re/SeVFZo</a><br>
            <div class="im"><br>
              <br>
              On Tue, 28 May 2013 11:26:30 +0900<br>
              Shinae Woo &lt;<a moz-do-not-send="true"
                href="mailto:shinae2012@gmail.com">shinae2012@gmail.com</a>&gt;
              wrote:<br>
              <br>
              &gt; Hello, all.<br>
              &gt;<br>
              &gt; I play the dpdk-1.2.3r1 with examples.<br>
              &gt;<br>
              &gt; But I can not achieve the line-rate packet receive
              performance,<br>
              &gt; and the performance is not scale with multiple ports.<br>
              &gt;<br>
              &gt; For example, in example l2fwd, I have tested two
              cases with 2 ports, and 4<br>
              &gt; ports,<br>
              &gt; using belowed command line each<br>
              &gt;<br>
              &gt; ./build/l2fwd -cf -n3 -- -p3<br>
              &gt; ./build/l2fwd -cf -n3 -- -pf<br>
              &gt;<br>
              &gt; But both cases, the aggregated performance are not
              scale.<br>
              &gt;<br>
              &gt; == experiments environments ==<br>
              &gt; - Two Intel 82599 NICs (total 4 ports)<br>
              &gt; - Intel Xeon X5690 &nbsp;@ 3.47GHz * 2 (total 12 cores)<br>
              &gt; - 1024 * 2MB hugepages<br>
              &gt; - Linux 2.6.38-15-server<br>
              &gt; - Each ports receiving 10Gbps of traffic of 64 bytes
              packets, 14.88Mpps.<br>
              &gt;<br>
            </div>
            &gt; *1. Packet forwarding performance*<br>
            <div>
              <div class="h5">&gt;<br>
                &gt; In 2 ports case, &nbsp;receive performance is 13Mpps,<br>
                &gt; In 4 ports case, &nbsp;not 26Mbps, only 16.8Mpps.<br>
                &gt;<br>
                &gt; Port statistics
                ====================================<br>
                &gt; Statistics for port 0
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4292256<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6517396<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2224776<br>
                &gt; Statistics for port 1
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;4291840<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6517044<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2225556<br>
                &gt; Aggregate statistics
                ===============================<br>
                &gt; Total packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;8584128<br>
                &gt; Total packets received: &nbsp; &nbsp; &nbsp; 13034472<br>
                &gt; Total packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; 4450332<br>
                &gt;
                ====================================================<br>
                &gt;<br>
                &gt; Port statistics
                ====================================<br>
                &gt; Statistics for port 0
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1784064<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2632700<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;848128<br>
                &gt; Statistics for port 1
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1784104<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2632196<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;848596<br>
                &gt; Statistics for port 2
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3587616<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5816344<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2200176<br>
                &gt; Statistics for port 3
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3587712<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;5787848<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2228684<br>
                &gt; Aggregate statistics
                ===============================<br>
                &gt; Total packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10743560<br>
                &gt; Total packets received: &nbsp; &nbsp; &nbsp; 16869152<br>
                &gt; Total packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; 6125608<br>
                &gt;
                ====================================================<br>
                &gt;<br>
              </div>
            </div>
            &gt; *2. Packet receiving performance*<br>
            <div class="HOEnZb">
              <div class="h5">&gt; I fix the codes for only receiving
                packets (not forwarding),<br>
                &gt; the performance is still not scalable as each
                13.3Mpps, 18Mpps.<br>
                &gt;<br>
                &gt; Port statistics
                ====================================<br>
                &gt; Statistics for port 0
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6678860<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Statistics for port 1
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6646120<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Aggregate statistics
                ===============================<br>
                &gt; Total packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Total packets received: &nbsp; &nbsp; &nbsp; 13325012<br>
                &gt; Total packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt;
                ====================================================<br>
                &gt;<br>
                &gt; Port statistics
                ====================================<br>
                &gt; Statistics for port 0
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3129624<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Statistics for port 1
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3131292<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Statistics for port 2
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6260908<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Statistics for port 3
                ------------------------------<br>
                &gt; Packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Packets received: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;6238764<br>
                &gt; Packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt; Aggregate statistics
                ===============================<br>
                &gt; Total packets sent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0<br>
                &gt; Total packets received: &nbsp; &nbsp; &nbsp; 18760640<br>
                &gt; Total packets dropped: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0<br>
                &gt;
                ====================================================<br>
                &gt;<br>
                &gt; The question is that<br>
                &gt; 1. How I can achieve each port receiving full
                14.88Mpps ?<br>
                &gt; &nbsp; &nbsp; What might be the bottleneck in current
                environment?<br>
                &gt; 2. Why the performance using multiple ports is not
                scale?<br>
                &gt; &nbsp; &nbsp; I guess doubling ports shows the doubling the
                receiving performance,<br>
                &gt; &nbsp; &nbsp; but it shows not. I am curious about what is
                limiting the packet<br>
                &gt; receivng performance.<br>
                &gt;<br>
                &gt; Thanks,<br>
                &gt; Shinae<br>
                <br>
              </div>
            </div>
            <span class="HOEnZb"><font color="#888888">--<br>
                SAKURA Internet Inc. / Senior Researcher<br>
                Naoto MATSUMOTO &lt;<a moz-do-not-send="true"
                  href="mailto:n-matsumoto@sakura.ad.jp">n-matsumoto@sakura.ad.jp</a>&gt;<br>
                SAKURA Internet Research Center &lt;<a
                  moz-do-not-send="true"
                  href="http://research.sakura.ad.jp/" target="_blank">http://research.sakura.ad.jp/</a>&gt;<br>
                <br>
              </font></span></blockquote>
        </div>
        <br>
      </div>
    </blockquote>
  </body>
</html>

--------------040303000004080805070607--