From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Amit Prakash Shukla <amitprakashs@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"kevin.laatz@intel.com" <kevin.laatz@intel.com>,
"conor.walsh@intel.com" <conor.walsh@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Vidya Sagar Velumuri <vvelumuri@marvell.com>,
"g.singh@nxp.com" <g.singh@nxp.com>,
"sachin.saxena@oss.nxp.com" <sachin.saxena@oss.nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
Jerin Jacob <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>,
Jerin Jacob <jerinjacobk@gmail.com>
Subject: RE: [EXTERNAL] Re: [PATCH v4] doc: announce changes to dma device structures
Date: Wed, 16 Jul 2025 04:29:33 +0000 [thread overview]
Message-ID: <SJ4PPFEA6F74CA2063FBA6C2C962FC8CC02A656A@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com> (raw)
In-Reply-To: <aHZi3mRo7UNbYbvD@bricha3-mobl1.ger.corp.intel.com>
>ZjQcmQRYFpfptBannerEnd
>On Wed, Jul 31, 2024 at 06:06:33PM +0200, Thomas Monjalon wrote:
>> 31/07/2024 13:01, Thomas Monjalon:
>> > 30/07/2024 19:27, Jerin Jacob:
>> > > On Tue, Jul 30, 2024 at 8:25 PM Amit Prakash Shukla
>> > > <amitprakashs@marvell.com> wrote:
>> > > >
>> > > > A new flag RTE_DMA_CAPA_QOS will be introduced to advertise dma
>> > > > device's QoS capability. In order to support the parameters for
>> > > > this flag, new fields will be added in rte_dma_info and
>> > > > rte_dma_conf structures to get device supported priority levels
>> > > > and to configure the required priority level.
>> > > >
>> > > > Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
>> > > > Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
>> > >
>> > >
>> > > Acked-by: Jerin Jacob <jerinj@marvell.com>
>> >
>> > Acked-by: Thomas Monjalon <thomas@monjalon.net>
>>
>> The RFC and the deprecation notices are sent a bit late.
>> We cannot conclude there is consensus.
>>
>> I propose to raise it to the techboard if an ABI breakage is still required for
>24.11.
>> As dmadev is quite new, I don't think it is big issue.
>>
>No objection to changing the structures. However, for the actual
>implementation we'll have to review the changes to ensure they are clear
>enough to allow potential alternative implementations. For example, I worry
>about just having one "QoS" flag defined - how would we manage if different
>QoS schemes are implemented by various hw vendors in different ways?
>
>For the notice about structure changes though:
>Acked-by: Bruce Richardson <bruce.richardson@intel.com>
This feature was renamed because it required consideration of advanced scheduling schemes,
Strict priority support was added at a later stage.
https://inbox.dpdk.org/dev/20241011101236.1467783-1-vattunuru@marvell.com/
prev parent reply other threads:[~2025-07-16 4:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 12:49 [PATCH] doc: announce dmadev new capability addition Vamsi Attunuru
2024-07-29 15:20 ` Jerin Jacob
2024-07-29 17:17 ` Morten Brørup
2024-07-31 10:24 ` Thomas Monjalon
2024-07-30 12:10 ` [PATCH v2] doc: announce changes to dma device structures Amit Prakash Shukla
2024-07-30 12:53 ` [PATCH v3] " Amit Prakash Shukla
2024-07-30 14:46 ` [PATCH v4] " Amit Prakash Shukla
2024-07-30 17:27 ` Jerin Jacob
2024-07-31 11:01 ` Thomas Monjalon
2024-07-31 16:06 ` Thomas Monjalon
2025-07-15 14:17 ` Bruce Richardson
2025-07-16 4:29 ` Vamsi Krishna Attunuru [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=SJ4PPFEA6F74CA2063FBA6C2C962FC8CC02A656A@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com \
--to=vattunuru@marvell.com \
--cc=amitprakashs@marvell.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=g.singh@nxp.com \
--cc=gmuthukrishn@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=thomas@monjalon.net \
--cc=vvelumuri@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).