All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nai-Hsien" <dennis@loop.com.tw>
To: lartc@vger.kernel.org
Subject: [LARTC] poor performance for building route cache
Date: Wed, 24 May 2006 12:45:43 +0000	[thread overview]
Message-ID: <0a4701c67f2f$f8b48b50$0102000a@loop.com.tw> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 844 bytes --]

I did a test shown as following diagram. (The DUT is running Linux with NAPI ethernet driver.)
I add 1000 routes into DUT then use the Smartbits
port1 to send packets (with destinations to all the 1000 networks) to the DUT then receive
them back from the port 2. The packets are sending in a rate that is much lower than half of
throughput of the DUT.

The DUT will lose some packets if the DUT has empty route cache before the packets are sent.
Once the DUT builds the route cache, the DUT can properly forward all packets to the other port
without any loose.

I guess that the issue is caused by heavy loading for building route cache.
I just doubt that the system can have such poor performance for building route cache.
Does anybody have any comment? Thank you.


Smartbits port 1 ----------- DUT ------------ Smartbits port2

[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2006-05-24 12:45 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='0a4701c67f2f$f8b48b50$0102000a@loop.com.tw' \
    --to=dennis@loop.com.tw \
    --cc=lartc@vger.kernel.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.