DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Vamsi Attunuru <vattunuru@marvell.com>, <fengchengwen@huawei.com>,
	<dev@dpdk.org>, <kevin.laatz@intel.com>, <jerinj@marvell.com>,
	<anoobj@marvell.com>
Subject: Re: [RFC] dmadev: add QoS capability
Date: Mon, 29 Jul 2024 14:27:11 +0100	[thread overview]
Message-ID: <ZqeYr5QHmCSeMZ-i@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F5BA@smartserver.smartshare.dk>

On Mon, Jul 29, 2024 at 03:14:55PM +0200, Morten Brørup wrote:
> > From: Vamsi Attunuru [mailto:vattunuru@marvell.com]
> > Sent: Monday, 29 July 2024 13.56
> > 
> > Some DMA controllers support QoS at HW command queue level to
> > differentiate the performance on different HW queues based on
> > the priority configured. Patch adds required fields in dmadev
> > structures to get hardware supported priority levels and the
> > provision to configure the priority from the applications.
> 
> Do we foresee anything more advanced than Strict Priority scheduling for DMA anytime in the future?
> 
> If not, then consider calling this new capability Prioritization (CAPA_PRIO) instead of Quality Of Service (CAPA_QOS). Then we don't need to add and describe QoS parameters for a more advanced QoS scheduling algorithm (e.g. the "weight" for weighted fair queueing).
> 

There could be more than just regular prioritization settings involved, so
I think it's best to leave some options open. Even with just a
"prioritization" setting, it could be used as a weighting vs strict priority.
Question is whether in such a case - of a single-value number for high vs
low priority - it's better to explicitly separate out a weight priority vs
a strict priority, or give a simpler interface by allowing just a single
number value.

/Bruce

  reply	other threads:[~2024-07-29 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 11:55 Vamsi Attunuru
2024-07-29 13:14 ` Morten Brørup
2024-07-29 13:27   ` Bruce Richardson [this message]
2024-07-29 13:53     ` Morten Brørup
2024-07-29 14:47       ` Vamsi Krishna Attunuru

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=ZqeYr5QHmCSeMZ-i@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=mb@smartsharesystems.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 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).