DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Kevin Yan <Kevin.Yan@mavenir.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK qos support for 40G port
Date: Fri, 4 Aug 2017 09:57:11 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <BN6PR11MB158548B205DC3BFF07D8B1C8F8B60@BN6PR11MB1585.namprd11.prod.outlook.com>

Hi Kevin,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kevin Yan
> Sent: Friday, August 4, 2017 2:55 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] DPDK qos support for 40G port
> 
> Hi,
>                 I have  a question about dpdk qos feature, in rte_sched.h,

<snip>...

>                 rate is type of uint32_t, but if physical port rate is 40G bit/s, which is
> 5G byte/s, 5G already exceed the max value of uint32_t, so I doult that 40G is
> not supported by dpdk qos lib, or any error of my understanding?
> 

Yes, your understanding is correct, currently the port rate in bytes per second needs to be represented as 32-bit number.

So, we can currently do single port with 10GbE and 25GbE rate, but not single port of 40GbE or 100GbE. Please note that we can do 40GbE as 4 ports of 10GbE each, which is a very common configuration for 40GbE.

This limitation is not trivial to remove, i.e. more code is needed to remove this limitation than just changing the rate data type to uint64_t.

Thanks for your feedback. Good to know that we should upgrade this library to support 40GbE rates sooner rather than later.

>                 Thanks and waiting for your reply!
> 
> 
> BRs,
> Kevin
> 

Regards,
Cristian

  reply	other threads:[~2017-08-04  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  1:54 Kevin Yan
2017-08-04  9:57 ` Dumitrescu, Cristian [this message]
2017-08-07  4:42   ` Kevin Yan
2017-08-18 11:24     ` Dumitrescu, Cristian
2017-08-18 17:21       ` Stephen Hemminger
2017-08-18 18:05         ` Dumitrescu, Cristian
2017-08-23  5:37       ` Kevin Yan

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=3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=Kevin.Yan@mavenir.com \
    --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).