From: Thomas Monjalon <thomas@monjalon.net>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/1] mempool/octeontx2: fix mempool creation failure
Date: Mon, 08 Jul 2019 11:54:42 +0200 [thread overview]
Message-ID: <4039147.TUYuIJoDKq@xps> (raw)
In-Reply-To: <BYAPR18MB2424F1905703A1FC22635051C8F60@BYAPR18MB2424.namprd18.prod.outlook.com>
08/07/2019 07:25, Jerin Jacob Kollanukkaran:
> From: vattunuru@marvell.com <vattunuru@marvell.com>
> Subject: [PATCH v1 1/1] mempool/octeontx2: fix mempool creation failure
>
> Actually it is v2.
At least, it is weel threaded with previous v1 :)
> v2..v1:
> # Fixed git-check-log.sh issues
> # Updated git comments for "when this issue happens?"
> # Change the name of the patch
> # Add Fixes tag
>
> > From: Vamsi Attunuru <vattunuru@marvell.com>
> >
> > Fix npa pool range errors observed while creating mempool, this issue
> > happens when mempool objects are from different mem segments.
> >
> > During mempool creation, octeontx2 mempool driver populates pool range
> > fields before enqueuing the buffers. If any enqueue or dequeue operation
> > reaches npa hardware prior to the range field's HW context update, those
> > ops result in npa range errors. Patch adds a routine to read back HW context
> > and verify if range fields are updated or not.
> >
> > Fixes: e5271c507aeb ("mempool/octeontx2: add remaining slow path ops")
> >
> > Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied, thanks
prev parent reply other threads:[~2019-07-08 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 10:33 [dpdk-dev] [PATCH v1 1/1] mempool/octeontx2: fix npa pool range errors vattunuru
2019-07-07 14:21 ` Jerin Jacob Kollanukkaran
2019-07-07 17:24 ` Thomas Monjalon
2019-07-08 4:47 ` [dpdk-dev] [PATCH v1 1/1] mempool/octeontx2: fix mempool creation failure vattunuru
2019-07-08 5:25 ` Jerin Jacob Kollanukkaran
2019-07-08 9:54 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4039147.TUYuIJoDKq@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=vattunuru@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.