From: Jesper Dangaard Brouer <brouer@redhat.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: brouer@redhat.com, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org
Subject: Re: [bpf-next PATCH 4/7] bpf: sockmap sample, report bytes/sec
Date: Tue, 9 Jan 2018 14:27:53 +0100 [thread overview]
Message-ID: <20180109142753.4ec376b1@redhat.com> (raw)
In-Reply-To: <20180108180558.13647.13464.stgit@john-Precision-Tower-5810>
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?
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-01-09 13:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 18:04 [bpf-next PATCH 0/7] sockmap sample updates John Fastabend
2018-01-08 18:05 ` [bpf-next PATCH 1/7] bpf: refactor sockmap sample program update for arg parsing John Fastabend
2018-01-09 13:30 ` Jesper Dangaard Brouer
2018-01-09 16:10 ` John Fastabend
2018-01-08 18:05 ` [bpf-next PATCH 2/7] bpf: add sendmsg option for testing BPF programs John Fastabend
2018-01-08 18:05 ` [bpf-next PATCH 3/7] bpf: sockmap sample, use fork() for send and recv John Fastabend
2018-01-09 23:54 ` Daniel Borkmann
2018-01-08 18:05 ` [bpf-next PATCH 4/7] bpf: sockmap sample, report bytes/sec John Fastabend
2018-01-09 13:27 ` Jesper Dangaard Brouer [this message]
2018-01-09 16:16 ` John Fastabend
2018-01-08 18:06 ` [bpf-next PATCH 5/7] bpf: sockmap sample add base test without any BPF for comparison John Fastabend
2018-01-08 18:06 ` [bpf-next PATCH 6/7] bpf: sockmap put client sockets in blocking mode John Fastabend
2018-01-08 18:06 ` [bpf-next PATCH 7/7] bpf: sockmap set rlimit John Fastabend
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=20180109142753.4ec376b1@redhat.com \
--to=brouer@redhat.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.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).