Dave,
Thanks for your explanation!
In my opinion, it depends on what the "is_mp_safe" flag actually means. If all
the functions are actually thread-safe and these barrier synchronization calls
are required mainly for debugging, then I suggest the following:
#if CLIB_DEBUG > 0
if (!c->is_mp_safe
It’s merged. Please let me know if all ok now.
--a
> On 31 Oct 2019, at 23:55, Andrew Yourtchenko via Lists.Fd.Io
> wrote:
>
> Elias,
>
> Thanks for telling! I have cherry-picked
> https://gerrit.fd.io/r/#/c/vpp/+/23164/ and will merge it tomorrow.
>
> --a
>
>>> On 31 Oct 2019, at 19:18,
FYI,
I have recently started to use the buildx experimental feature in docker
(>=19.03).
it looks interesting as it is designed on purpose for building
multi-platform images,
and manages to reuse the same dockerfile for as many platforms as supported
by qemu (in theory).
I'm not quite sure yet ab
Hi all.
My lab follow this guide : https://wiki.fd.io/view/VPP/Tutorial_DPDK_and_MacSwap
Interface info
>
> vpp# show int
> Name Idx State MTU (L3/IP4/IP6/MPLS) Counter
> Count
> TenGigabitEthernet5e/0/0 1 up 9000/0/0/0 rx
> packets
Hi Damjan,
>> My comment bellow is that only 1) is really needed to build VPP, people can
>> decide to use own build system like buildroot or yocto and invoke cmake
>> directly, and completely ignore 2) and 3
Correct me if I am wrong, purpose of build-data/platforms/*.mk (except vpp.mk)
can b
Yes, now it works. Thank you!
/ Elias
On Fri, 2019-11-01 at 08:42 +0100, Andrew 👽 Yourtchenko wrote:
> It’s merged. Please let me know if all ok now.
>
> --a
>
> > On 31 Oct 2019, at 23:55, Andrew Yourtchenko via Lists.Fd.Io <
> > ayourtch=gmail@lists.fd.io> wrote:
> >
> > Elias,
> >
> >
> On 1 Nov 2019, at 09:57, Nitin Saxena wrote:
>
> Hi Damjan,
>
>>> My comment bellow is that only 1) is really needed to build VPP, people
>>> can decide to use own build system like buildroot or yocto and invoke cmake
>>> directly, and completely ignore 2) and 3
> Correct me if I am wron
Hi Damjan,
>> I don’t understand why you cannot specify your preferred set of args
>> directly in the buildroot makefile...
We can do that. I thought (1) and (2) is the recommended way of cross compiling
VPP. So if I understand correctly all Makefiles in build-data/platforms/ are
intended for n
> On 1 Nov 2019, at 12:14, Nitin Saxena wrote:
>
> Hi Damjan,
>
>>> I don’t understand why you cannot specify your preferred set of args
>>> directly in the buildroot makefile...
> We can do that. I thought (1) and (2) is the recommended way of cross
> compiling VPP. So if I understand corr
If you want to discover which functions are thread-safe the hard way, feel free
to disable the barrier syncs as shown. Please don’t push a patch like that.
c->is_mp_safe != 0 means that a human being has looked at the code and done at
least a cursory survey to make sure that vpp won’t have an ac
Understood.
Thanks
Nitin
> -Original Message-
> From: Damjan Marion
> Sent: Friday, November 1, 2019 5:13 PM
> To: Nitin Saxena
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [EXT] [vpp-dev] cross-compilation support
>
>
>
> > On 1 Nov 2019, at 12:14, Nitin Saxena wrote:
> >
> > Hi Damj
Hi,
If you are interested in or working with DPDK, the community is hosting
their DPDK NA Summit, November 12-13 at the Computer History Museum, in
Mountain View.
The program and registration details can be found here:
https://events19.linuxfoundation.org/events/dpdknorthamerica2019/
Regards,
T
Hi all,
I am trying to build some API client code against a copy of the
master branch I pulled a couple of days ago (ee74376 ip: refactor ip4_mtrie
to use atomic store-release). It seems like some required headers are not
getting installed for plugins.
E.g. - the LACP plugin header lacp.api.h has
In my code based on the user changing the ipsec backend I need to update the
node in my "encrypt" slots (for v4 and v6). I am calling
vlib_node_add_next_with_slot to do this; however, the function isn't doing what
I want.
Basically vlib_node_add_next_with_slot does the following:
if ((p = ha
Just for record purposes, here are the configs I figured out on l2 gretap +
ipsec transport mode. The other party config is similar with proper changes
in ip, mac address and spi. Make sure spi matches. Otherwise, pkt will be
punted on the receiving side.
set int state eth0 up
set int ip address e
Just for record purposes, we did not continue trying this R740-R230 setup.
We moved to R740-R740 setup. We did not see this phy nic down issue. It
seems some compatibility bug within R230 + some nic.
On Sun, Oct 20, 2019 at 9:37 PM Balaji Venkatraman via Lists.Fd.Io wrote:
> I see in the log of
Shows you how often people have actually hacked graph arcs.
One way to handle it would be to add an explicit vlib_node_delete_next (vm,
node_index, next_node_index) to clean out the hash table entry / set the arc
next node index to ~0 or some such.
If that sounds OK, I can build it or you can b
Hanlin,
I’ve been working on Envoy/Vcl integration for a while now and Ping Yu has
joined me in this effort. Vcl works fine with a large, multi-threaded
application like Envoy, although the integration has had its challenges. We are
getting very close to trying to upstream the code.
-stephen
Hi,
We have registred this issue int NAT plugin and i am already working on solving
the issue. If you need to post any additional content please do so on jira
issue VPP-1795 (https://jira.fd.io/browse/VPP-1795). You can monitor progress
through the jira ticket.
Thank you.
Best regards,
Filip
Hi stephenIt's great. Is there any performance data comparing with the kernel path now?
Regards,Hanlin
发自网易邮箱大师
On 11/2/2019 06:42，Stephen Belair (sbelair) via Lists.Fd.Io wrote：
Hanlin,
I’ve been working on Env
20 matches
Mail list logo
