On Thu, 4 Nov 2021 11:03:21 +
"Ananyev, Konstantin" wrote:
> Hi Ben,
>
> I also don’t think 64 is a common case here.
> For such cases we probably should think up some different approach for the
> reassembly table.
Larger values make it easier to DoS the IP fragment table.
See the Linux fr
...@trinitycyber.com; Stefan Baranoff
Subject: Re: [dpdk-dev] Overriding rte_config.h
Thanks for the clarification.
I agree bumping RTE_LIBRTE_IP_FRAG_MAX_FRAG to 8 probably makes sense to easily
support jumbo frames.
The other use case we have is supporting highly fragmented UDP. To support
this we were
Thanks for the clarification.
I agree bumping RTE_LIBRTE_IP_FRAG_MAX_FRAG to 8 probably makes sense to
easily support jumbo frames.
The other use case we have is supporting highly fragmented UDP. To support
this we were increasing to 64 (next power of 2) based on a 64K UDP max and
a link MTU of
> > > > > On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> > > > > > With the transition to meson, what is the best way to provide
> > > > > > custom values
> > > > > > to parameters in rte_config.h? When using makefiles, (from memory,
> > > > > > I
> > > > > > think) we used co
On Tue, Nov 02, 2021 at 12:24:43PM +, Ananyev, Konstantin wrote:
>
> > > > On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> > > > > With the transition to meson, what is the best way to provide custom
> > > > > values
> > > > > to parameters in rte_config.h? When using makefil
> > > On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> > > > With the transition to meson, what is the best way to provide custom
> > > > values
> > > > to parameters in rte_config.h? When using makefiles, (from memory, I
> > > > think) we used common_base as a template that was
On Tue, Nov 02, 2021 at 11:20:04AM +, Ananyev, Konstantin wrote:
>
> > On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> > > With the transition to meson, what is the best way to provide custom
> > > values
> > > to parameters in rte_config.h? When using makefiles, (from memory
> On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> > With the transition to meson, what is the best way to provide custom values
> > to parameters in rte_config.h? When using makefiles, (from memory, I
> > think) we used common_base as a template that was copied in as a
> > replac
On Fri, Oct 29, 2021 at 09:48:30AM -0400, Ben Magistro wrote:
> With the transition to meson, what is the best way to provide custom values
> to parameters in rte_config.h? When using makefiles, (from memory, I
> think) we used common_base as a template that was copied in as a
> replacement for de
With the transition to meson, what is the best way to provide custom values
to parameters in rte_config.h? When using makefiles, (from memory, I
think) we used common_base as a template that was copied in as a
replacement for defconfig_x86 Our current thinking is to apply a
locally maintained
10 matches
Mail list logo
