From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f48.google.com (mail-pg0-f48.google.com [74.125.83.48]) by dpdk.org (Postfix) with ESMTP id EA6937CB4 for ; Fri, 18 Aug 2017 19:22:11 +0200 (CEST) Received: by mail-pg0-f48.google.com with SMTP id y129so68231650pgy.4 for ; Fri, 18 Aug 2017 10:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=xEhLVOMYzQiPC8yfleotqlZSpvy/1badEAn1eN2WNEs=; b=gWBW8K5s2/fSs31uVUzGZaR7eo9KkZazHaVFou73E44L1p0l6OIWKnGJEpNSxLp9B+ M0zt3k7m5zrlFkRRgd4MIiHiL6s7qiauSqo/HP8EU/QbKBn89qvnNBWu+0xVj7xxsxdk KVAQf/RFgq8Jh2p+eG/p2hZ9SU5KSCVMSlSMVNxz32xLghaG1a42EyVJ7dHM9dWGARZW oMWPvKtYe6TFQuh4u3PS0by5h3YpG4XWW93btjRrRneu+j8xco3aArYI9pIfM6H/h4tJ 3FaNtNbsSGLjV1Njf3DhauU1TgTL1rLCCHOhqChj9XA6vz38fXLPJ0AHEMbxjNDc9PCT BQEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=xEhLVOMYzQiPC8yfleotqlZSpvy/1badEAn1eN2WNEs=; b=XDH/OZeJL7eNTU0VWgYZKGHJwkD0zl0LlM4zSCZRULKqvUuxhv2vW4mwcWfAc0arO6 4z6+RwXV55xnrPaE7iqZufdWRvpCYeXvziSD8BRDyCA+vaCnbl0SCS3/97xKo3xEhiHi a2629AeQYf8KkIBXGXbHgKg/79lSVKT2Nu2d6tS+c8sbLrIxYIpY4DCdrN+JaTl9LE2l lyoKFdt1gqEqtBO7wv4JmDqDQ9fG5Gwc5mWOWbL6Zy9kFWQzjU37dsJ6muzLd0nwGtyf MoHBkKmXzOI6oC5cqkrsy6mR2nfYC1tJ3NRR1Sz56kAhqPeZRU4ANeTMS7Sda8fnYJ/l +OeQ== X-Gm-Message-State: AHYfb5hBns2K/RgOSCG+EGLfmXwDyODsf4qo3kx0X+OTIuF6VFRpoi6Q uZ6jQaqc2q3gyJyO X-Received: by 10.84.195.3 with SMTP id i3mr10654687pld.380.1503076931230; Fri, 18 Aug 2017 10:22:11 -0700 (PDT) Received: from xeon-e3 (76-14-207-240.or.wavecable.com. [76.14.207.240]) by smtp.gmail.com with ESMTPSA id l2sm10518990pgc.27.2017.08.18.10.22.10 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 18 Aug 2017 10:22:11 -0700 (PDT) Date: Fri, 18 Aug 2017 10:21:58 -0700 From: Stephen Hemminger To: "Dumitrescu, Cristian" Cc: Kevin Yan , "dev@dpdk.org" Message-ID: <20170818102158.1d5f7d0f@xeon-e3> In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BA9C525@IRSMSX108.ger.corp.intel.com> References: <3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com> <3EB4FA525960D640B5BDFFD6A3D891267BA9C525@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] DPDK qos support for 40G port X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Aug 2017 17:22:12 -0000 On Fri, 18 Aug 2017 11:24:12 +0000 "Dumitrescu, Cristian" wrote: > 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 > Maybe it is time to deprecate existing QoS since it has so many fixed limits and start a new version which supports up to 400G and many more classes. Something that integrated better with your new QoS framework.