From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
dev@dpdk.org
Subject: Re: [PATCH 2/2] common/cnxk: split XAQ counts
Date: Tue, 19 Sep 2023 22:30:14 +0530 [thread overview]
Message-ID: <CALBAE1M=ENJrV-JONZkityU3KtgYqsmgU=4OD=RA8LQ-JxUdog@mail.gmail.com> (raw)
In-Reply-To: <20230909165747.7458-2-pbhagavatula@marvell.com>
On Sun, Sep 10, 2023 at 1:46 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Split XAQ counts into reserved and cached to allow more events
> to be inflight.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-eventdev/for-main. Thanks
commit e227b98adbbacde663fbf0cafe512a1a123adef1 (HEAD -> for-main,
origin/for-main, origin/HEAD)
Author: Pavan Nikhilesh <pbhagavatula@marvell.com>
Date: Sat Sep 9 22:27:47 2023 +0530
common/cnxk: fix XAQ limits
Split XAQ counts into reserved and cached to allow more events
to be in flight.
Fixes: c3320d21b475 ("event/cnxk: use LMTST for enqueue new burst")
Cc: stable@dpdk.org
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
commit 87007fcc6a0c7274226dcb80675986fdcab57de8
Author: Pavan Nikhilesh <pbhagavatula@marvell.com>
Date: Sat Sep 9 22:27:46 2023 +0530
event/cnxk: fix context flush in port cleanup
Flush currently held flow context during event port cleanup.
Fixes: e8594de2731d ("event/cnxk: implement event port quiesce function")
Cc: stable@dpdk.org
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
prev parent reply other threads:[~2023-09-19 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 16:57 [PATCH 1/2] event/cnxk: flush flow context on cleanup pbhagavatula
2023-09-09 16:57 ` [PATCH 2/2] common/cnxk: split XAQ counts pbhagavatula
2023-09-19 17:00 ` Jerin Jacob [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='CALBAE1M=ENJrV-JONZkityU3KtgYqsmgU=4OD=RA8LQ-JxUdog@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).