I agree with Ye, it's a pain to configure ip4, ip6 output, unicast and
multicast. If my device is used with only physical interfaces and tunnel
encap/decap of outer ip4/ip6 is used, interface-output is nice to have. I
don't know enough about VPP to suggest what changes are needed, but I am
Folks,
The Docker Hub Rate Limit issue has been resolved (details below) and
the FD.io CI jobs are operating normally. Please let me know if you
encounter any errant failure signatures.
Thanks to Vanessa & Trishan for their help resolving the outage.
Cheers,
-daw-
%<
Docker Hub
vppapigen has 4 types:
['Enum', 'Typedef', 'Using', 'Union']
Using and Union seem to be hints to vpp_papi for converting to/from the
wire format. Is there a use case where they need to be exposed to a
high-level client?
If I am creating too much noise for the list, let me know. This is
> On 19.11.2020., at 16:14, Solis JR, M. (Mauricio) via lists.fd.io
> wrote:
>
> Hi,
>
> I am trying to figure out where VPP allocates memory for the DPDK TX queues.
>
> In dpdk/common.c
> I am seeing a call to: vec_validate_aligned (xd->tx_queues, xd->tx_q_used -
> 1,
> Can we clarify the .api (syntax) so that enums are separate from flags?
> Today, everything is rendered (at least in Python) as an (enum|aenum).IntFlag.
>
> Here is a sample of how that an enum looks like in python:
> class rx_mode(enum.IntFlag): # u32:
> UNKNOWN = 0
> POLLING = 1
>
Ole,
Can we clarify the .api (syntax) so that enums are separate from flags?
Today, everything is rendered (at least in Python) as an
(enum|aenum).IntFlag.
Here is a sample of how that an enum looks like in python:
class rx_mode(enum.IntFlag): # u32:
UNKNOWN = 0
POLLING = 1
Hi,
I am trying to figure out where VPP allocates memory for the DPDK TX queues.
In dpdk/common.c
I am seeing a call to: vec_validate_aligned (xd->tx_queues, xd->tx_q_used - 1,
CLIB_CACHE_LINE_BYTES)
I'm not if this allocates memory for each queue since I'm not seeing a size
other than for
> On 19.11.2020., at 08:31, Benoit Ganne (bganne) via lists.fd.io
> wrote:
>
>> We are mixing today 2 different things: packaging for specific distro and
>> making sure that code can work with specific build/runtime dependencies.
>
> Good point. So basically maintaining something like
>
Dave,
> Before we deprecate vat - and the vat plugins - it would be nice to solve
> the CLI problem. In particular, to make the "binary-api" debug CLI work in
> some reasonable way with vat2.
Agree, I think a proper answer to that question is required gating for vat2
ever becoming a
Dear Ole,
Before we deprecate vat - and the vat plugins - it would be nice to solve
the CLI problem. In particular, to make the "binary-api" debug CLI work in
some reasonable way with vat2.
I have operational configuration files of considerable length full of stuff
like this:
binary-api
Hi vpp devs,
I have been trying to run vpp on latest master branch with mlx 5 enables on
centos 8.2 machine .
I have downloaded and installed the mellanox driver from
url:https://www.mellanox.com/products/infiniband-drivers/linux/mlnx_ofed and
installed the following dependencies:
#yum install
Hi,
Problems:
- VAT requires hand-written code for CLI and print routines
- VAT only supports parts of the API (people have forgotten to add VAT code
when adding new APIs)
- API trace supports generating "SCRIPT" code for VAT, but that is also partly
supported, and the trace handlers overlap
thinks for your reply, I got it, but it is a little inconvenient if one
want to add some features base on interface.
Instead, he should add features on ip4-output/ip6-ouput arc or
ip4-unicast/ip6-unicast twice, but still there are packets get through
interface but ip4/6 nodes.
在
13 matches
Mail list logo
