> -Original Message-
> From: alangordonde...@gmail.com [mailto:alangordonde...@gmail.com]
> Sent: Wednesday, September 13, 2017 11:16 AM
> To: Kantecki, Tomasz
> Cc: dev@dpdk.org; Alan Dewar
> Subject: [PATCH v2] sched: make RED scaling configurable
>
> From:
...@gmail.com [mailto:alangordonde...@gmail.com]
Sent: Friday, September 1, 2017 2:42 PM
To: Kantecki, Tomasz
Cc: dev@dpdk.org; Alan Dewar
Subject: [PATCH] sched: make RED scaling configurable
From: Alan Dewar
The RED code stores the maximum threshold is a 32-bit integer as a pseudo
fixed-point
Hi Thomas,
> > 12s is long for a functional test. We are used to have tests of less than
> > 1s.
> > Do you think this magnitude order can be achieved for red tests?
>
> This is a real challenge :) Let me take another look into it.
I had a 2nd look into this test suite and reducing time for fun
Hi Thomas,
> 12s is long for a functional test. We are used to have tests of less than 1s.
> Do you think this magnitude order can be achieved for red tests?
This is a real challenge :) Let me take another look into it.
Regards,
Tomasz
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Is it possible to split them in
> - short functional tests
> - long run / perf tests
> ?
> So we could keep some basic tests in fast_test.
> I expect that tests which are not part of fast_test won't be run often or in
> eno
istian
> Sent: Tuesday, May 24, 2016 6:08 PM
> To: Thomas Monjalon ; Kantecki, Tomasz
>
> Cc: dev at dpdk.org
> Subject: RE: fast red autotest
>
> Hi Thomas,
>
> From my side, I am OK to remove RED from the fast autotest, as long as it is
> kept available as part
> > > > The skeleton aims to show a minimal piece of code (but bigger than
> > > > hello world).
> > > > For any other usage, I think the "l2fwd" name is more appropriate.
> > > >
> > > > > +DIRS-y += skeleton-cat
> > > >
> > >
> > > We have used skeleton app as basis for this sample code. It is j
> > +Basic Forwarding sample application is a simple *skeleton* example of
> > +a forwarding application. It has been extended to make use of CAT via
> > +extended command line options and linking against the libpqos library.
>
> The skeleton aims to show a minimal piece of code (but bigger than h
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> If there is nothing specific in DPDK for PQos, why writing an example in
> DPDK?
The example makes it much easier to use the technology with DPDK.
> Maybe the example should be better in the library itself.
The library in question (ht
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Are you OK with concept behind V2 PQoS patch as described above?
>
> So you mean that PQoS don't really need some DPDK integration?
> You just want to show how to use it with DPDK?
You are correct. The technology can be used withou
> EAL should not depend on the PQoS library.
> Please could you hook the command line parsing and help to add these new
> options from outside?
Thanks for the feedback - we heard about dependency problem from a few sources.
> The command line options may be convenient in some cases but not
> stra
11 matches
Mail list logo
