From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Fastabend <john.fastabend@gmail.com>
Subject: Re: [bpf-next PATCH 4/7] bpf: sockmap sample, report bytes/sec
Date: Tue, 9 Jan 2018 08:16:43 -0800
Message-ID: <0b1092f0-889d-ad8b-7678-5037f3181f95@gmail.com>
References: <20180108180302.13647.13866.stgit@john-Precision-Tower-5810>
 <20180108180558.13647.13464.stgit@john-Precision-Tower-5810>
 <20180109142753.4ec376b1@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: ast@kernel.org, daniel@iogearbox.net, netdev@vger.kernel.org
To: Jesper Dangaard Brouer <brouer@redhat.com>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pf0-f181.google.com ([209.85.192.181]:41166 "EHLO
        mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932998AbeAIQQ5 (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 9 Jan 2018 11:16:57 -0500
Received: by mail-pf0-f181.google.com with SMTP id j3so5033078pfh.8
        for <netdev@vger.kernel.org>; Tue, 09 Jan 2018 08:16:57 -0800 (PST)
In-Reply-To: <20180109142753.4ec376b1@redhat.com>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 01/09/2018 05:27 AM, Jesper Dangaard Brouer wrote:
> On Mon, 08 Jan 2018 10:05:58 -0800
> John Fastabend <john.fastabend@gmail.com> wrote:
> 
>> Report bytes/sec sent as well as total bytes. Useful to get rough
>> idea how different configurations and usage patterns perform with
>> sockmap.
> 
> Why BYTES per second, and not BITS per sec?
> 

Memory bandwidths is commonly reported in MB/s not bits/sec and
also application throughput tends to be reported in B/s as well.

In general it seemed more natural to map application performance
to B/s. A toggle would be easy enough to report in both or just
bits. On the other hand iperf/netperf seem to report bits per sec.

.John