From: Vincent JARDIN <vincent.jardin-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: L3FWD LPM IP lookup performance question
Date: Tue, 24 Sep 2013 17:53:22 +0200 [thread overview]
Message-ID: <5241B572.5090009@6wind.com> (raw)
In-Reply-To: <CAGeT4PLM1mG8NsFwWL06NMz7KeR641FDAYbqK171SpLO7XzqMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
I do not know any open source implementation of an efficient LPM. FYI,
some data with a commercial one:
-> up to 160Mpps, the bottleneck was the IOs, not the CPU.
http://www.6wind.com/products/6windgate-protocols/ip-forwarding/
Best regards,
Vincent
On 24/09/2013 15:53, Jun Han wrote:
> Hello,
>
> We are trying to benchmark L3FWD application and have a question regarding
> the IP lookup algorithm as we expect the bottleneck to be at the lookup.
> Could someone let us know how efficient the lookup algorithm that L3FWD is
> using (e.g, LPM)? We are asking because we want to obtain highest L3
> forwarding performance number, and we might need to change the lookup
> method if the current LPM method is not as efficient.
>
> Thank you very much,
>
> Jun
>
next prev parent reply other threads:[~2013-09-24 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:53 L3FWD LPM IP lookup performance question Jun Han
[not found] ` <CAGeT4PLM1mG8NsFwWL06NMz7KeR641FDAYbqK171SpLO7XzqMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-24 15:53 ` Vincent JARDIN [this message]
[not found] ` <5241B572.5090009-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-26 21:16 ` Chris Pappas
[not found] ` <CAE4G5iqr4w9COPRr--LzkaZtLaqZTuww1wjDkCFOkaL8VG8ApA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-30 10:11 ` Vincent JARDIN
-- strict thread matches above, loose matches on Subject: below --
2013-10-01 8:57 Vladimir Medvedkin
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=5241B572.5090009@6wind.com \
--to=vincent.jardin-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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.