DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gladchun, Glenn" <ggladchun@idirect.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK QoS scheduler changes, are we there yet?
Date: Wed, 30 Oct 2019 18:35:13 +0000	[thread overview]
Message-ID: <3FD7CF4F-3FEA-4557-9D5C-3D30A6A8331E@idirect.net> (raw)

Hi guys,

I stumbled upon this 11 month old post (https://narkive.com/ZwBXg4Xe) that goes over future enhancements to the scheduler.  All of them are vital, and I am especially interested in 16 TCs per pipe… Christian and/or Jasvinder, is the future here yet in some tangible shape or form?

Thanks,

Glenn G

This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. 
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of 
this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender.

             reply	other threads:[~2019-10-30 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 18:35 Gladchun, Glenn [this message]
2019-10-31 15:13 ` Ferruh Yigit
2019-10-31 17:45   ` Singh, Jasvinder
2019-11-01 19:32     ` Gladchun, Glenn
2019-11-04  7:48     ` David Marchand
2019-11-04 10:09       ` Singh, Jasvinder
  -- strict thread matches above, loose matches on Subject: below --
2019-10-30 15:32 Gladchun, Glenn

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=3FD7CF4F-3FEA-4557-9D5C-3D30A6A8331E@idirect.net \
    --to=ggladchun@idirect.net \
    --cc=dev@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).