On Sat, Nov 16, 2019 at 7:56 PM <pbhagavat...@marvell.com> wrote: > > From: Pavan Nikhilesh <pbhagavat...@marvell.com> > > Update OcteonTx limitaion with max mempool size used.
Please squash this patch to the first patch and change all occurrence of OcteonTx with OCTEON TX. > > Signed-off-by: Pavan Nikhilesh <pbhagavat...@marvell.com> > --- > doc/guides/eventdevs/octeontx.rst | 7 +++++++ > doc/guides/nics/octeontx.rst | 7 +++++++ > 2 files changed, 14 insertions(+) > > diff --git a/doc/guides/eventdevs/octeontx.rst > b/doc/guides/eventdevs/octeontx.rst > index ab36a36e0..587b7a427 100644 > --- a/doc/guides/eventdevs/octeontx.rst > +++ b/doc/guides/eventdevs/octeontx.rst > @@ -139,3 +139,10 @@ follows: > > When timvf is used as Event timer adapter event schedule type > ``RTE_SCHED_TYPE_PARALLEL`` is not supported. > + > +Max mempool size > +~~~~~~~~~~~~~~~~ > + > +Max mempool size when using OcteonTx Eventdev (SSO) should be limited to > 128K. > +When running dpdk-test-eventdev on OcteonTx the application can limit the > +number of mbufs by using the option ``--pool_sz 131072`` > diff --git a/doc/guides/nics/octeontx.rst b/doc/guides/nics/octeontx.rst > index 3c19c912d..00098a3b2 100644 > --- a/doc/guides/nics/octeontx.rst > +++ b/doc/guides/nics/octeontx.rst > @@ -174,3 +174,10 @@ The OCTEON TX SoC family NICs support a maximum of a 32K > jumbo frame. The value > is fixed and cannot be changed. So, even when the ``rxmode.max_rx_pkt_len`` > member of ``struct rte_eth_conf`` is set to a value lower than 32k, frames > up to 32k bytes can still reach the host interface. > + > +Maximum mempool size > +~~~~~~~~~~~~~~~~~~~~ > + > +The maximum mempool size supplied to Rx queue setup should be less than 128K. > +When running testpmd on OcteonTx the application can limit the number of > mbufs > +by using the option ``--total-num-mbufs=131072``. > -- > 2.24.0 >
