DPDK usage discussions
 help / color / mirror / Atom feed
From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: Kapil Adhikesavalu <kapil20084@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK QOS
Date: Wed, 7 Sep 2016 12:48:42 +0000	[thread overview]
Message-ID: <54CBAA185211B4429112C315DA58FF6DEBF148@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAAu6pRd76V-JgNiM+0AcgxoMmn3=Am-FoZg-vy3vMhx5mz5atw@mail.gmail.com>

Hi Kapil,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Kapil
> Adhikesavalu
> Sent: Tuesday, September 6, 2016 8:29 AM
> To: users@dpdk.org
> Subject: [dpdk-users] DPDK QOS
> 
> Hello,
> 
> I currently receive both control and data traffic on my dpdk port. I want to
> classify the packets and assign more priority to the control packets; is there a
> way to put the control packets in one queue and give it a higher priority than
> the other queue(s).


DPDK QoS scheduler prioritizes the packets, enqueue them into queues and schedule their transmission  based on available bandwidth as per configured SLAs.
In your case, the traffic belonging to different classes (control, data) needs to be appropriately queued in. For that, you can learn from the classification stage of the QoS which set the "sched" field of the mbuf.  Later, this field can be consumed to determine the priority of the packets (i.e. traffic class & queue ) and buffer them into respective queues. Depending upon your application, you can select scheduling process to determine which packet is to be transmitted next.  


> From the dpdk QOS section, i see Qos metering and scheduling can be done
> only for the traffic sent out of the port (Tx) ? or am i missing something ?

QoS traffic metering is applied to the input packet as a measure of how much the user/flow currently exceeds its pre-allocated bandwidth, while QoS Scheduling (traffic management) refers to prioritizing the output packets in the case the available traffic exceeds the available bandwidth based on pre-configured SLAs.


> Regards
> Kapil.

Jasvinder

      reply	other threads:[~2016-09-07 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  7:29 Kapil Adhikesavalu
2016-09-07 12:48 ` Singh, Jasvinder [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=54CBAA185211B4429112C315DA58FF6DEBF148@IRSMSX103.ger.corp.intel.com \
    --to=jasvinder.singh@intel.com \
    --cc=kapil20084@gmail.com \
    --cc=users@dpdk.org \
    /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).