From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BBFA6C3A59F for ; Thu, 29 Aug 2019 23:21:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8DC6A21874 for ; Thu, 29 Aug 2019 23:21:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=networkplumber-org.20150623.gappssmtp.com header.i=@networkplumber-org.20150623.gappssmtp.com header.b="Ie4C9ynj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728162AbfH2XVT (ORCPT ); Thu, 29 Aug 2019 19:21:19 -0400 Received: from mail-pf1-f179.google.com ([209.85.210.179]:34444 "EHLO mail-pf1-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727673AbfH2XVT (ORCPT ); Thu, 29 Aug 2019 19:21:19 -0400 Received: by mail-pf1-f179.google.com with SMTP id b24so3202562pfp.1 for ; Thu, 29 Aug 2019 16:21:19 -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=qylN9i4xaRuIu/7tRX9HS4iq7VIt3+GlRK/+MNDbrNg=; b=Ie4C9ynjICNmD8YI/lrwt+CuSoJ4jS2F45DzqTE5d/yp5txlNNfrkIfxw070/P0ESM djnJjJZFKTlq5Huyr7zYeGh1+u+qvmHRacfJgfkzgeTC9PpGF+wFoCDSiRg7oceXCUKO BxeV3BPhy82yYFWNMzh3As0D36lVKI4L/hNfHp46O05tHiXnh0IpR2JByJnElnVBkaAm gjvllZBT9LPT7hJOFIeq5P7Xs1MNPb7eebGQ4DW5FptSBQEPLHmfZh7NF5c5C48kieIr hAQtrRby4yOAAVvLGEzUGd4rTqS3megv7gd/kwEr4/TB6CUzokDCrfr5tdzvG3CTjTG1 Inkg== 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=qylN9i4xaRuIu/7tRX9HS4iq7VIt3+GlRK/+MNDbrNg=; b=QG9xA2PBZS7VSz3c0J7Hd66+rmS1ikX6LV/i+2BU7mNsu3BVbJWgYWoS2xEv2FDzHN yvwBKZ1CygIhYaRTF+DVLYVFK+w6yAmgsjHIJjH7agdutiStG+cN3U1B29BPFMx8Igki +weYhA8TvI5/Rsvt5nk8dJicm5zPI+bj4DjSSOgRu2MapKPtWstau6AJQ1ukAwU+pL5m vmpdKeQhSvYGCDZGBDsxD97ERWylvgPXF3/RVsDvlYEESJy2I4YK14JPwzJRhALsZTzE a38qZn+ax2nr2ovDLdjGWvWi7sakGrW3JRYX/AwGzHsAPaQ7pZ8A8WwdK1TWGlax4lZs mv9w== X-Gm-Message-State: APjAAAU4kBF4vVnMX3kByza5bs9x4LfBdCFkgyUJH+HqZ/3/QS9djgPU NtftKbjuRmoGDJek7+ccAu2YWA== X-Google-Smtp-Source: APXvYqwzUfSkqIcFKaXDQZeFwsZiRgKFyEpVVe9g6ARNrlQQDUlfVtgVtSD5Foj7gS5xRWRl8LPyKg== X-Received: by 2002:aa7:96dc:: with SMTP id h28mr14608679pfq.86.1567120878639; Thu, 29 Aug 2019 16:21:18 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id x128sm4088989pfd.52.2019.08.29.16.21.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Aug 2019 16:21:18 -0700 (PDT) Date: Thu, 29 Aug 2019 16:21:15 -0700 From: Stephen Hemminger To: David Dai Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, zdai@us.ibm.com Subject: Re: [v1] iproute2: police: support 64bit rate and peakrate in tc utility Message-ID: <20190829162115.2644488d@hermes.lan> In-Reply-To: <1567032776-1118-1-git-send-email-zdai@linux.vnet.ibm.com> References: <1567032776-1118-1-git-send-email-zdai@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, 28 Aug 2019 17:52:56 -0500 David Dai wrote: > For high speed adapter like Mellanox CX-5 card, it can reach upto > 100 Gbits per second bandwidth. Currently htb already supports 64bit rate > in tc utility. However police action rate and peakrate are still limited > to 32bit value (upto 32 Gbits per second). Taking advantage of the 2 new > attributes TCA_POLICE_RATE64 and TCA_POLICE_PEAKRATE64 from kernel, > tc can use them to break the 32bit limit, and still keep the backward > binary compatibility. > > Tested-by: David Dai > Signed-off-by: David Dai This needs to go to iproute2-next not iproute2