[dpdk-dev] [PATCH] i40e: fix the issue of wrongly reporting descriptor done

2015-07-30 06:08, Helin Zhang: > Header buffer address for header split will be filled with the > physical address for DMA, which is actually not needed at all, > as header split hasn't been supported. Hardware requires the > least bit of header address which is 'Descriptor Done' bit when > write b

[dpdk-dev] [PATCH] e1000: fix the issue of wrongly reporting descriptor done

2015-07-30 10:39, Wenzhuo Lu: > Header buffer address for header split will be filled with the physical > address for DMA, which is actually not needed at all, as header split > hasn't been supported. Hardware requires the least bit of header address > which is 'Descriptor Done' bit when write back

[dpdk-dev] [PATCH] app test: fix mempool cache_size not match limited cache_size

2015-07-29 11:22, Yong Liu: > In previous setting, mempool size and cache_size are both 32. > This is not satisfied with cache_size checking rule by now. > Cache size should less than CONFIG_RTE_MEMPOOL_CACHE_MAX_SIZE and mempool > size / 1.5. Sorry I don't really understand this explanation. >

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

2015-08-02 20:58, Wiles, Keith: > On 8/2/15, 3:44 PM, "Thomas Monjalon" wrote: > > >2015-08-02 19:10, Wiles, Keith: > >> On 8/2/15, 12:15 PM, "Thomas Monjalon" > >>wrote: > >> >2015-06-06 19:04, Keith Wiles: > >> >> +# Log level use: RTE_LOG_XXX > >> >> +# XXX = NOOP, EMERG, ALERT, CRIT, ERR,

[dpdk-dev] [PATCH] ethdev: fix ABI breakage in lro code

2015-07-17 01:22, Vlad Zolotarov: > On 07/13/15 13:26, John McNamara wrote: > > Fix for ABI breakage introduced in LRO addition. Moves > > lro bitfield to the end of the struct/member. > > > > Fixes: 8eecb3295aed (ixgbe: add LRO support) > > > > Signed-off-by: John McNamara > > Acked-by: Vlad Zol

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

2015-08-02 19:10, Wiles, Keith: > On 8/2/15, 12:15 PM, "Thomas Monjalon" wrote: > >2015-06-06 19:04, Keith Wiles: > >> +# Log level use: RTE_LOG_XXX > >> +# XXX = NOOP, EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO or DEBUG > >> +# Look in rte_log.h for others if any. > >> +# > > > >I think t

[dpdk-dev] [PATCH] eal/linux: fix negative value for undetermined numa_node

On Mon, Aug 03, 2015 at 09:46:54AM +0800, Liang, Cunming wrote: > According to the API definition, if the socket could not be determined, a > default of zero will take. > The '-1' is returned when the port_id value is out of range. Yes, but when I asked the exact same question and was told the doc

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

On 8/2/15, 3:44 PM, "Thomas Monjalon" wrote: >2015-08-02 19:10, Wiles, Keith: >> On 8/2/15, 12:15 PM, "Thomas Monjalon" >>wrote: >> >2015-06-06 19:04, Keith Wiles: >> >> +# Log level use: RTE_LOG_XXX >> >> +# XXX = NOOP, EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO or >>DEBUG >> >> +# Look

[dpdk-dev] [PATCH v2] log:Change magic number on RTE_LOG_LEVEL to an enum name

On Sun, 2 Aug 2015 16:40:24 -0500 Keith Wiles wrote: > Config files used RTE_LOG_LEVEL=8 to set log level to DEBUG. Using > a the RTE_LOG_ is easier to maintain. > > Converted the RTE_LOG_ define into a enum of values with > the same names to reduce maintaining the define values. > > T

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

2015-06-06 19:04, Keith Wiles: > --- a/config/common_bsdapp > +++ b/config/common_bsdapp > @@ -93,12 +93,18 @@ CONFIG_RTE_MAX_NUMA_NODES=8 > CONFIG_RTE_MAX_MEMSEG=256 > CONFIG_RTE_MAX_MEMZONE=2560 > CONFIG_RTE_MAX_TAILQ=32 > -CONFIG_RTE_LOG_LEVEL=8 > CONFIG_RTE_LOG_HISTORY=256 > CONFIG_RTE_EAL

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

On 8/2/15, 2:10 PM, "dev on behalf of Wiles, Keith" wrote: >On 8/2/15, 12:15 PM, "Thomas Monjalon" wrote: > >>2015-06-06 19:04, Keith Wiles: >>> --- a/config/common_bsdapp >>> +++ b/config/common_bsdapp >>> @@ -93,12 +93,18 @@ CONFIG_RTE_MAX_NUMA_NODES=8 >>> CONFIG_RTE_MAX_MEMSEG=256 >>> CONFI

[dpdk-dev] [PATCH] log:Change magic number on RTE_LOG_LEVEL to a define

On 8/2/15, 12:15 PM, "Thomas Monjalon" wrote: >2015-06-06 19:04, Keith Wiles: >> --- a/config/common_bsdapp >> +++ b/config/common_bsdapp >> @@ -93,12 +93,18 @@ CONFIG_RTE_MAX_NUMA_NODES=8 >> CONFIG_RTE_MAX_MEMSEG=256 >> CONFIG_RTE_MAX_MEMZONE=2560 >> CONFIG_RTE_MAX_TAILQ=32 >> -CONFIG_RTE_LOG

[dpdk-dev] [PATCH v2] log:Change magic number on RTE_LOG_LEVEL to an enum name

Config files used RTE_LOG_LEVEL=8 to set log level to DEBUG. Using a the RTE_LOG_ is easier to maintain. Converted the RTE_LOG_ define into a enum of values with the same names to reduce maintaining the define values. The change is to use an enum in place of a magic number, plus we get th

[dpdk-dev] dpdk 2.0 - how to build the documentation

On 8/2/15, 12:41 AM, "dev on behalf of Thomas Monjalon" wrote: >2015-08-02 09:39, Kevin Wilson: >> I have downloaded dpdk-2.0.0.tar.gz from dpdk.org >> How do I build the documentation (pdf files)? > >They are available here: > http://dpdk.org/doc/archives/dpdk-2.0/pdf/guides/ >If you want

[dpdk-dev] dpdk 2.0 - how to build the documentation

2015-08-02 09:39, Kevin Wilson: > I have downloaded dpdk-2.0.0.tar.gz from dpdk.org > How do I build the documentation (pdf files)? They are available here: http://dpdk.org/doc/archives/dpdk-2.0/pdf/guides/ If you want to build them: make doc-guides-pdf You'll need these packages:

[dpdk-dev] dpdk 2.0 - how to build the documentation

Hi, I have downloaded dpdk-2.0.0.tar.gz from dpdk.org How do I build the documentation (pdf files)? Regards, Kevin