All of lore.kernel.org
 help / color / mirror / Atom feed
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 1/7] bpf: refactor sockmap sample program update for arg parsing
Date: Tue, 9 Jan 2018 14:30:14 +0100	[thread overview]
Message-ID: <20180109143014.26f203f9@redhat.com> (raw)
In-Reply-To: <20180108180507.13647.62367.stgit@john-Precision-Tower-5810>

On Mon, 08 Jan 2018 10:05:07 -0800
John Fastabend <john.fastabend@gmail.com> 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>
> ---
>  samples/sockmap/sockmap_user.c |  142 +++++++++++++++++++++++++++++-----------
>  1 file changed, 103 insertions(+), 39 deletions(-)
> 
> diff --git a/samples/sockmap/sockmap_user.c b/samples/sockmap/sockmap_user.c
> index 7cc9d22..5cbe7a5 100644
> --- a/samples/sockmap/sockmap_user.c
> +++ b/samples/sockmap/sockmap_user.c
> @@ -35,6 +35,8 @@
>  #include <assert.h>
>  #include <libgen.h>
>  
> +#include <getopt.h>
> +
>  #include "../bpf/bpf_load.h"
>  #include "../bpf/bpf_util.h"
>  #include "../bpf/libbpf.h"
> @@ -46,15 +48,39 @@
>  #define S1_PORT 10000
>  #define S2_PORT 10001
>  
> -static int sockmap_test_sockets(int rate, int dot)
> +/* global sockets */
> +int s1, s2, c1, c2, p1, p2;
> +
> +static const struct option long_options[] = {
> +	{"help",	no_argument,		NULL, 'h' },
> +	{"cgroup",	required_argument,	NULL, 'c' },
> +	{"rate",	required_argument,	NULL, 'r' },
> +	{"verbose",	no_argument,		NULL, 'v' },
> +	{0, 0, NULL, 0 }
> +};
> +
> +static void usage(char *argv[])
> +{
> +	int i;
> +
> +	printf(" Usage: %s --cgroup <cgroup_path>\n", argv[0]);
> +	printf(" options:\n");
> +	for (i = 0; long_options[i].name != 0; i++) {
> +		printf(" --%-12s", long_options[i].name);
> +		if (long_options[i].flag != NULL)
> +			printf(" flag (internal value:%d)\n",
> +				*long_options[i].flag);
> +		else
> +			printf(" -%c\n", long_options[i].val);
> +	}
> +	printf("\n");
> +}
> +

I love that you are using --long-options :-)

Acked-by: Jesper Dangaard Brouer <brouer@redhat.com>

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2018-01-09 13:30 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 [this message]
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
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=20180109143014.26f203f9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.