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

Thanks, Cristian

-----Original Message-----
From: Dumitrescu, Cristian [mailto:cristian.dumitrescu@intel.com]
Sent: Friday, August 18, 2017 7:24 PM
To: Kevin Yan <Kevin.Yan@mavenir.com>; dev@dpdk.org
Subject: RE: DPDK qos support for 40G port

Hi Kevin,

> Hi Cristian,
> Sorry to bother again, could you give suggestions/hints of code change
> to support single 40G port?  Because  in our setup, we will use single
> 40G port (Intel XL710) as the network interface.
>
> Or is there any workaround to bypass the limitation?(we are not
> willing to use 4*10G setup)
>
> Thanks.
>

Probably the easiest thing to do as workaround to support single port of 40GbE rate is to change the code so that each credit is equivalent to 2 bytes instead of one. This is likely to result in some scheduling accuracy loss, but it can be implemented relatively quickly while avoiding complex code changes.

Regards,
Cristian

________________________________
Please Note: My email address is changing. Starting May 1st 2017 my email will solely be my Mavenir email firstname.lastname@mavenir.com. All other prior email accounts will become inactive. To ensure continuity, please send all emails to my Mavenir email ID which is currently active and available for use.


This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to security@mavenir.com. Thank You. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects.

      parent reply	other threads:[~2017-08-23  5:37 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
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 [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=BN6PR11MB1585FF66F32C57F5787AD381F8850@BN6PR11MB1585.namprd11.prod.outlook.com \
    --to=kevin.yan@mavenir.com \
    --cc=cristian.dumitrescu@intel.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).