From: Martin KaFai Lau <kafai@fb.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: <borkmann@iogearbox.net>, <ast@kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [bpf-next PATCH v3 1/7] bpf: refactor sockmap sample program update for arg parsing
Date: Fri, 12 Jan 2018 23:19:04 -0800 [thread overview]
Message-ID: <20180113071903.poxnsamgabsfb5ko@kafai-mbp> (raw)
In-Reply-To: <20180112050617.5823.7863.stgit@john-Precision-Tower-5810>
On Thu, Jan 11, 2018 at 09:06:17PM -0800, John Fastabend wrote:
> sockmap sample program takes arguments from cmd line but it reads them
> in using offsets into the array. Because we want to add more arguments
> in the future lets do proper argument handling.
>
> Also refactor code to pull apart sock init and ping/pong test. This
> allows us to add new tests in the future.
>
> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
One nit below.
Acked-by: Martin KaFai Lau <kafai@fb.com>
> ---
[ ... ]
> @@ -280,12 +333,21 @@ int main(int argc, char **argv)
> return err;
> }
>
> - err = sockmap_test_sockets(rate, dot);
> + err = sockmap_init_sockets();
> if (err) {
> fprintf(stderr, "ERROR: test socket failed: %d\n", err);
> - return err;
> + goto out;
> }
> - return 0;
> +
> + err = forever_ping_pong(rate, verbose);
> +out:
> + close(s1);
> + close(s2);
> + close(p1);
> + close(p2);
> + close(c1);
> + close(c2);
close(cg_fd);
> + return err;
> }
>
> void running_handler(int a)
>
next prev parent reply other threads:[~2018-01-13 7:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 5:06 [bpf-next PATCH v3 0/7] sockmap sample update John Fastabend
2018-01-12 5:06 ` [bpf-next PATCH v3 1/7] bpf: refactor sockmap sample program update for arg parsing John Fastabend
2018-01-13 7:19 ` Martin KaFai Lau [this message]
2018-01-12 5:06 ` [bpf-next PATCH v3 2/7] bpf: add sendmsg option for testing BPF programs John Fastabend
2018-01-13 7:30 ` Martin KaFai Lau
2018-01-12 5:06 ` [bpf-next PATCH v3 3/7] bpf: sockmap sample, use fork() for send and recv John Fastabend
2018-01-13 7:31 ` Martin KaFai Lau
2018-01-13 7:33 ` Martin KaFai Lau
2018-01-12 5:07 ` [bpf-next PATCH v3 4/7] bpf: sockmap sample, report bytes/sec John Fastabend
2018-01-13 7:34 ` Martin KaFai Lau
2018-01-12 5:07 ` [bpf-next PATCH v3 5/7] bpf: sockmap sample add base test without any BPF for comparison John Fastabend
2018-01-13 7:34 ` Martin KaFai Lau
2018-01-12 5:07 ` [bpf-next PATCH v3 6/7] bpf: sockmap put client sockets in blocking mode John Fastabend
2018-01-13 7:34 ` Martin KaFai Lau
2018-01-12 5:08 ` [bpf-next PATCH v3 7/7] bpf: sockmap set rlimit John Fastabend
2018-01-13 7:35 ` Martin KaFai Lau
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=20180113071903.poxnsamgabsfb5ko@kafai-mbp \
--to=kafai@fb.com \
--cc=ast@kernel.org \
--cc=borkmann@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