On 27. 05. 2020. 13:48, Singh, Jasvinder wrote:
>
>> -Original Message-
>> From: dev On Behalf Of Hrvoje Habjanic
>> Sent: Tuesday, May 26, 2020 6:25 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] [PATCH] rte_sched: correctly free allocated subport
>> memory
>>
>> In function rte_sched_subp
ss
Hi, Guys
I am learning data structure defined by dpdk framework and I noticed
a data structure definition below:
enum rte_eth_hash_function {
RTE_ETH_HASH_FUNCTION_DEFAULT = 0,
RTE_ETH_HASH_FUNCTION_TOEPLITZ, /**< Toeplitz */
RTE_ETH_HASH_FUNCTION_SIMPLE_XOR, /**< Simple XOR
On Fri, May 29, 2020 at 03:19:45PM +0100, Burakov, Anatoly wrote:
> External Email
>
> --
> On 29-May-20 2:19 PM, Harman Kalra wrote:
>
> > > if (ret < 0)
> > > rte_exit(EXIT_FAILURE, "Invalid L3FWD pa
> > > I also share Olivier's concern about consuming 3 bits in ol_flags for
> > > that feature.
> > > Can it probably be squeezed somehow?
> > > Let say we reserve one flag that this information is present or not, and
> > > re-use one of rx-only fields for store additional information
> > > (pack
4 matches
Mail list logo