DPDK usage discussions
 help / color / mirror / Atom feed
From: "Александр Киселев" <kiselev99@gmail.com>
To: yingzhi <kaitoy@qq.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Question regarding packet availability
Date: Thu, 28 Jul 2016 23:09:34 +0300	[thread overview]
Message-ID: <CAMKNYbz6b=WR=j8M__ni5=XfNXjEwg-oPMePan-=fviOGgC28Q@mail.gmail.com> (raw)
In-Reply-To: <tencent_00F43648467DCCF27BF76A74@qq.com>

Hi.

You can use KNI interfaces to redirect the control plane traffic whether
it's a bgp or any other routing protocol traffic to the KNI while
forwarding data plane traffic using dpdk. It will allow your linux routing
daemon to receive route updates without having a dedicated physical
interface. After that you should find a way to redistribute the received
routes back to your dpdk forwarding engine. To do that you can use linux
netlink interface or quagga's FPM interface. The bird also has a API to
export routes, but I am not shure.

четверг, 28 июля 2016 г. пользователь yingzhi написал:

> Hi All,
>
>
> I'm new to DPDK and would like to ask some quick questions.
> We are trying to develop a Load Balance solution that take advantage of
> ECMP with BGP, so there is a BGP process running on our LB node, and we'd
> like to use DPDK to improve packet processing performance.
> The questions is, if DPDK bind to a interface, can it still
> sending/receiving BGP packets or I need a separate interface dedicated for
> BGP? In the later case, can the BGP process still aware of the DPDK bond
> port's network and announce that network to uplink router?
>
>
> Any comment/advice is appreciated.
>
>
> Thanks in advance.



-- 
--
Kiselev Alexander

      parent reply	other threads:[~2016-07-28 20:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 10:00 yingzhi
2016-07-28 16:37 ` dave seddon
2016-07-28 20:09 ` Александр Киселев [this message]

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='CAMKNYbz6b=WR=j8M__ni5=XfNXjEwg-oPMePan-=fviOGgC28Q@mail.gmail.com' \
    --to=kiselev99@gmail.com \
    --cc=kaitoy@qq.com \
    --cc=users@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).