On 3/26/2024 12:55 PM, Sivaprasad Tummala wrote: > With modern CPUs, it is possible to have higher > CPU count thus we can have higher RTE_MAX_LCORES. > In DPDK sample applications, the current config > lcore options are hard limited to 255. > > The patchset fixes these constraints by allowing > all lcore IDs up to RTE_MAX_LCORES. Also the rx > queue IDs are increased to support up to 65535. > The port ID constraints were also fixed to support > up to RTE_MAX_ETHPORTS. > > v7: > - updated commit log with rx queue IDs > - changed format specifier to %PRIu16 > - removed patch unrelated changes > > v6: > - split queue_id, lcore_id and port_id changes as > separate patches. > - updated git commit description on individual > patches > > v5: > - updated lcore_id type to uint32_t > > v4: > - fixed build errors with queue_id type > in ipsec-secgw > > v3: > - updated queue_id type to uint16_t > > v2: > - fixed typo with lcore_id type in l3fwd > > Sivaprasad Tummala (14): > examples/l3fwd: fix queue ID restriction > examples/l3fwd-power: fix queue ID restriction > examples/l3fwd-graph: fix queue ID restriction > examples/ipsec-secgw: fix queue ID restriction > examples/l3fwd: fix lcore ID restriction > examples/l3fwd-power: fix lcore ID restriction > examples/l3fwd-graph: fix lcore ID restriction > examples/ipsec-secgw: fix lcore ID restriction > examples/qos_sched: fix lcore ID restriction > examples/vm_power_manager: fix lcore ID restriction > examples/l3fwd: fix port ID restriction > examples/l3fwd-power: fix port ID restriction > examples/l3fwd-graph: fix port ID restriction > examples/ipsec-secgw: fix port ID restriction >
Hi Thomas, I am aware we are very close to -rc3, but this patch series is from the previous release, can it be possible to include it to -rc3? Thanks, ferruh
