> On 13 Apr 2020, at 19:56, Dave Wallace wrote:
>
> ļ»æYes, that's exactly what I saw.
>
> I'm trying to figure out if the issue was actually related to the system
> clock / ntp or perhaps some weird form of corruption of the file metadata
> during the creation or extraction of the tarball.
T
Yes, that's exactly what I saw.
I'm trying to figure out if the issue was actually related to the system
clock / ntp or perhaps some weird form of corruption of the file
metadata during the creation or extraction of the tarball.
Thanks,
-daw-
On 4/13/2020 12:58 PM, Andrew š½ Yourtchenko wrote
The logs did look pretty weird - well before the message Paul sent there is a
slew of complaints about the checksums in a tarball being X seconds in the
future.
And it seems like that tarball is made earlier in the same job.
Does this correlate with what you saw ?
--a
> On 13 Apr 2020, at 17
Hi Chenmin,
Regarding your second question, some of the device drivers could mark buffers
for tx csum offload which is honored only if data is about to be delivered to
the network (or if some other action performed to the buffer requires csums to
be computed). Otherwise, if packets end up cons
This seemed to go away Friday evening (EDT) and it looks like it
happened twice since then although most jobs have been passing.
I'll keep an eye on it and see if I can figure out the root cause...
Thanks,
-daw-
On 4/11/2020 12:05 PM, Paul Vinciguerra wrote:
Jobs are consistently failing in th
[Edited Message Follows]
Hi experts,
I am confusing about the L4 checksum behavior in VPP. I noticed the code was
there for a very long time(more than 3 years) so I open this topic to see if
anybody knows the history and why.
* The first problem is in DPDK plugin and was introduced in commit d
--
hi all,
I've added two files, content is as follows:
*mk/machine/atom/rte. Vars. Mk*
# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2010-2014 Intel Corporation
#
# machine:
#
#Ā Ā - can define ARCH variable (overridden by cmdline value)
#Ā Ā - can define CROSS variable (overridden by cm
Hi,
I am trying to validate ipv6 reassembly on vpp 20.01. My observation isĀ that
fragmented packets which are terminatedĀ onĀ vpp are landing on shallow
reassembly ( *ip6-sv-reassembly)* node and not on full reassembly node (
*ip6-full-reassembly* ), So, full reassembly is not happening with defa
Hi experts,
I am confusing about the L4 checksum behavior in VPP. I noticed the code was
there for a very long time(more than 3 years) so I open this topic to see if
anybody knows the history and why.
The first problem is in DPDK plugin and was introduced in commit d81566ff92:
Disable for-us u
Hi,
I want to apply policer to all incoming packets on a particular interface. I
understood VPP policer and classify configuration.
But the classify table command need a mask .
Is there a way to apply policer configuration for *all* packets on an
interface? Is there any kind of wildcard configur
10 matches
Mail list logo
