> On Dec 3, 2019, at 12:56 PM, Ole Troan <otr...@employees.org> wrote:
>
> If you don't want that, wouldn't you just build something with a Trident 4?
> ;-)
Or Tofino, if you want to go that direction. Even then, the amount of
packet-processing (especially the edge/exception conditions) can overwhelm a
hardware-based approach.
I’ve recently seen architectures where a VPP-based solution is the “slow path”,
taking the exception traffic that a Tofino-based forwarder can’t handle.
But VPP is an open source project, and DPDK is also an open source project.
Similar technologies, but, at least to us, very a very different style of
interaction. I’m here to suggest that a different measure of “efficient use of
$PROJECT” can also be measured by the accomodation of patches.
We've had trouble getting bugs patched in DPDK drivers where we even provided a
pointer to the exact solution and/or code to fix.
Specifics, if you like:
• ixgbe x552 SFP+ link delay — We had to push multiple times and go as
far as to pester individuals (itself a violation of the ‘rules’ as contributors
are only supposed email d...@dpdk.org <mailto:d...@dpdk.org>, based on the
comment “Pleas avoid private emails” at the top of the MAINTAINERS file.
• i40e did not advertise support for scatter/gather on a PF, but did on
a VF. This was the quickest resolution: 11 days after submitting it, someone
emailed and said “OK”, so we enabled it.
https://bugs.dpdk.org/show_bug.cgi?id=92
• A month or two ago we submitted a report that the X557 1Gb copper
ports on the C3000 were advertising that they support higher speeds when they
do not. We haven’t heard a word back about it.
Perhaps this is similar to what Damjan referenced when he suggested
that the ixgbe driver seems largely unmaintained.
To be fair, these are all Intel, not Mellanox, but my point is, and entirely in
the converse to our experience with DPDK: VPP is has been entirely responsive
to submitted patches for 3 years running. We don’t get everything accepted,
(nor are we asking to) but we do have 160 commits which have been upstreamed.
This is dwarfed by Cisco, and Intel has about 100 more, but the point is not
how much we’ve contributed, but the relative ease of contribution to upstream
in DPDK .vs VPP.
Jim-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14775): https://lists.fd.io/g/vpp-dev/message/14775
Mute This Topic: https://lists.fd.io/mt/65218320/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
