From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Ashwin Sekhar T K <asekhar@marvell.com>, dpdk-dev <dev@dpdk.org>,
"Jerin Jacob" <jerinj@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
"Satha Koteswara Rao Kottidi" <skoteshwar@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
"Satheesh Paul" <psatheesh@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v3] devtools: add acronyms in dictionary for commit checks
Date: Wed, 3 Nov 2021 16:44:12 +0000 [thread overview]
Message-ID: <b3eebaa8-64a3-e00f-7b37-f7a535b1fa2d@intel.com> (raw)
In-Reply-To: <c2e1f85f-7ccc-ccf8-b594-f9bbfd884ffb@intel.com>
On 9/20/2021 11:32 AM, Ferruh Yigit wrote:
> On 9/20/2021 10:10 AM, Jerin Jacob wrote:
>> On Mon, Sep 20, 2021 at 2:37 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>>>
>>> On 9/17/2021 11:58 AM, Ashwin Sekhar T K wrote:
>>>> Update word list with Marvell specific acronyms.
>>>>
>>>> CPT -> Cryptographic Accelerator Unit
>>>> CQ -> Completion Queue
>>>> LBK -> Loopback Interface Unit
>>>> LMT -> Large Atomic Store Unit
>>>> MCAM -> Match Content Addressable Memory
>>>> NIX -> Network Interface Controller Unit
>>>> NPA -> Network Pool Allocator
>>>> NPC -> Network Parser and CAM Unit
>>>> ROC -> Rest Of Chip
>>>
>>> Out of curiosity, what is "rest of chip"?
>>
>> All the HW accelerators excluding the CPU cores.
>>
>
> Thanks.
>
>>>
>>>> RQ -> Receive Queue
>>>> RVU -> Resource Virtualization Unit
>>>> SQ -> Send Queue
>>>> SSO -> Schedule Synchronize Order Unit
>>>> TIM -> Timer Unit
>>>>
>>>> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
>>>
>
Hi David, Thomas,
Can we proceed with this patch if there is no more objection?
There are multiple 'cnxk' patches are using these acronyms,
it would be good the have them checked.
(Although I suspect Jerin already have the patch locally,
since there is no missuses in sent patches.)
patchwork:
https://patches.dpdk.org/project/dpdk/patch/20210917105839.270289-1-asekhar@marvell.com/
next prev parent reply other threads:[~2021-11-03 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:03 [dpdk-dev] [PATCH v1] " Ashwin Sekhar T K
2021-09-17 10:06 ` [dpdk-dev] [PATCH v2] " Ashwin Sekhar T K
2021-09-17 10:58 ` [dpdk-dev] [PATCH v3] " Ashwin Sekhar T K
2021-09-17 11:03 ` Jerin Jacob
2021-11-25 11:30 ` Thomas Monjalon
2021-09-17 12:55 ` Thomas Monjalon
2021-09-17 13:54 ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 14:05 ` Thomas Monjalon
2021-09-17 14:53 ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-17 16:15 ` Thomas Monjalon
2021-09-20 9:05 ` Ferruh Yigit
2021-09-20 9:19 ` Ashwin Sekhar Thalakalath Kottilveetil
2021-09-20 10:31 ` Ferruh Yigit
2021-09-20 9:07 ` [dpdk-dev] " Ferruh Yigit
2021-09-20 9:10 ` Jerin Jacob
2021-09-20 10:32 ` Ferruh Yigit
2021-11-03 16:44 ` Ferruh Yigit [this message]
2021-09-20 9:21 ` [dpdk-dev] [EXT] " Ashwin Sekhar Thalakalath Kottilveetil
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=b3eebaa8-64a3-e00f-7b37-f7a535b1fa2d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=kirankumark@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=thomas@monjalon.net \
/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).