From: Thomas Monjalon <thomas@monjalon.net>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: dev@dpdk.org, fengchengwen@huawei.com, kevin.laatz@intel.com,
bruce.richardson@intel.com, conor.walsh@intel.com,
gmuthukrishn@marvell.com, vvelumuri@marvell.com, g.singh@nxp.com,
sachin.saxena@oss.nxp.com, hemant.agrawal@nxp.com, dev@dpdk.org,
jerinj@marvell.com, vattunuru@marvell.com, anoobj@marvell.com,
mb@smartsharesystems.com, Jerin Jacob <jerinjacobk@gmail.com>
Subject: Re: [PATCH v4] doc: announce changes to dma device structures
Date: Wed, 31 Jul 2024 13:01:48 +0200 [thread overview]
Message-ID: <3321231.G96rZvMJ2N@thomas> (raw)
In-Reply-To: <CALBAE1NkQuJCj+qOsVy-cZ2baj1+UqNhgut6jEtQitapp6DW1w@mail.gmail.com>
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>
next prev parent reply other threads:[~2024-07-31 11:07 UTC|newest]
Thread overview: 10+ 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 [this message]
2024-07-31 16:06 ` Thomas Monjalon
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=3321231.G96rZvMJ2N@thomas \
--to=thomas@monjalon.net \
--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=vattunuru@marvell.com \
--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).