On Wed, Dec 12, 2018 at 4:12 AM John Biscevic <john.bisce...@bahnhof.net>
wrote:

> Hi Brian,
>
>
> I've successfully built the router plugin on 18.10 and "19.01"
>
>
> What errors are you encountering when you attempt to build it?
>
When following the instructions (doing the steps for running make, found in
router/README.md, right after all the ln -sf steps):

@@@@ Building netlink in
/usr/local/src/vpp/build-root/build-vpp_debug-native/netlink @@@@

make[1]: Entering directory
`/usr/local/src/vpp/build-root/build-vpp_debug-native/netlink'

  CC       librtnl/netns.lo

  CC       librtnl/rtnl.lo

  CC       librtnl/mapper.lo

  CC       test/test.lo

/usr/local/src/vpp/build-data/../netlink/librtnl/rtnl.c: In function
'rtnl_socket_open':

/usr/local/src/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: error:
'RTNLGRP_MPLS_ROUTE' undeclared (first use in this function)

     grpmask(RTNLGRP_NOTIFY) | grpmask(RTNLGRP_MPLS_ROUTE),

                                       ^

/usr/local/src/vpp/build-data/../netlink/librtnl/rtnl.c:269:39: note: each
undeclared identifier is reported only once for each function it appears in

/usr/local/src/vpp/build-data/../netlink/librtnl/netns.c:69:5: error:
'RTA_VIA' undeclared here (not in a function)

   _(RTA_VIA, via, 1)                            \

     ^

/usr/local/src/vpp/build-data/../netlink/librtnl/netns.c:82:13: note: in
definition of macro '_'

     .type = t, .unique = u,                     \

             ^

/usr/local/src/vpp/build-data/../netlink/librtnl/netns.c:86:3: note: in
expansion of macro 'ns_foreach_rta'

   ns_foreach_rta

   ^

make[1]: *** [librtnl/rtnl.lo] Error 1

make[1]: *** Waiting for unfinished jobs....

make[1]: *** [librtnl/netns.lo] Error 1

make[1]: Leaving directory
`/usr/local/src/vpp/build-root/build-vpp_debug-native/netlink'

make: *** [netlink-build] Error 2



Is this something you encountered? How did you resolve it?

Brian


>
> Kind regards,
>
> * John Biscevic*
> Systems Architect,  Bahnhof AB
> Mobile:  +46 76 111 01 24
> E-mail: * john.bisce...@bahnhof.net <john.bisce...@bahnhof.net>*
> ------------------------------
> *From:* vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of Brian
> Dickson <brian.peter.dick...@gmail.com>
> *Sent:* Wednesday, December 12, 2018 4:17 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vppsb-...@lists.fd.io
> *Subject:* [vpp-dev] vpp router plugin threads? (vpp + router + netlink +
> FRRouting)
>
> Greetings, VPP folks.
>
> I am continuing to work on my vpp + router-plugin (+FRRouting) set-up.
>
> I have things mostly working with very large routing tables (source from
> multiple BGP peers), but am having some challenges when trying to use
> multi-threaded (additional worker threads) for increasing overall VPP
> forwarding performance.
>
> When using just a single thread, the BGP peers take a long time to sync up
> but it is relatively stable. Forwarding performance on a 10G NIC (i40e
> driver and vfio-pci selected), is pretty decent, but I am interested in
> finding ways to improve performance (and getting things to the point where
> I can use a 40G card also in the system). The limit seems to be packets per
> second, and maxes out at about 11Mpps.
>
> The problem is, when I try to use worker threads, I start running into
> issues with rtnetlink buffers, and BGP, ICMP, ARP, etc, all become "flaky".
>
> My suspicion is that it has something to do with which thread(s) handle
> the netlink traffic, and which thread(s) handle the TCP port 179 (BGP)
> traffic, which needs to go via the tap-inject path to the kernel, and then
> to the BGP speaking application (FRR sub-unit "bgpd").
>
> Is there anyone who can provide information or advice on this issue?
>
> NB: the flakiness is in a COMPLETELY unloaded environment - no other
> traffic is being handled, nothing else is consuming CPU cycles. It is just
> the BGP traffic itself plus related stuff (ARP) and any diagnostic traffic
> I use (ping).
>
> Is this a case where I need to adjust the RSS to direct incoming packets
> to the right subset of cores, and do I also need to direct particular
> traffic (TCP 179) to the main core? Do I need to ensure anything else, like
> using a separate core (and set the core afinity with taskset -c ) for my
> BGP speaker?
>
> Any suggestions or advice would be greatly appreciated.
>
> Also, any updates on bringing netlink and router plugins into the main
> vppsb tree? Building them on anything other than 18.07 just doesn't work
> for me, and even on 18.07 is rather brittle, and I'm not 100% sure about
> the build steps, which actually involve passing CFLAGS in to make, which
> suggests something isn't quite right...
>
> Thanks in advance,
> Brian
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11586): https://lists.fd.io/g/vpp-dev/message/11586
Mute This Topic: https://lists.fd.io/mt/28729084/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to