public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@fb.com>
To: Brian Vazquez <brianvv@google.com>,
	Brian Vazquez <brianvv.kernel@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"David S . Miller" <davem@davemloft.net>
Cc: Stanislav Fomichev <sdf@google.com>,
	Petar Penkov <ppenkov@google.com>,
	Willem de Bruijn <willemb@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: [PATCH v2 bpf-next 9/9] selftests/bpf: add batch ops testing to array bpf map
Date: Thu, 21 Nov 2019 18:43:19 +0000	[thread overview]
Message-ID: <4688ba20-0730-7689-9332-aa0dcef5258e@fb.com> (raw)
In-Reply-To: <20191119193036.92831-10-brianvv@google.com>



On 11/19/19 11:30 AM, Brian Vazquez wrote:
> Tested bpf_map_lookup_batch() and bpf_map_update_batch()
> functionality.
> 
>    $ ./test_maps
>        ...
>          test_map_lookup_and_delete_batch_array:PASS
>        ...

The test is for lookup_batch() and update_batch()
and the test name and func name is lookup_and_delete_batch(),
probably rename is to lookup_and_update_batch_array()?

It would be good if generic lookup_and_delete_batch()
and delete_patch() can be tested as well.
Maybe tried to use prog_array?

> 
> Signed-off-by: Brian Vazquez <brianvv@google.com>
> Signed-off-by: Yonghong Song <yhs@fb.com>
> ---
>   .../map_lookup_and_delete_batch_array.c       | 119 ++++++++++++++++++
>   1 file changed, 119 insertions(+)
>   create mode 100644 tools/testing/selftests/bpf/map_tests/map_lookup_and_delete_batch_array.c
> 
> diff --git a/tools/testing/selftests/bpf/map_tests/map_lookup_and_delete_batch_array.c b/tools/testing/selftests/bpf/map_tests/map_lookup_and_delete_batch_array.c
> new file mode 100644
> index 0000000000000..cbec72ad38609
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/map_tests/map_lookup_and_delete_batch_array.c
> @@ -0,0 +1,119 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include <stdio.h>
> +#include <errno.h>
> +#include <string.h>
> +
> +#include <bpf/bpf.h>
> +#include <bpf/libbpf.h>
> +
> +#include <test_maps.h>
> +
> +static void map_batch_update(int map_fd, __u32 max_entries, int *keys,
> +			     int *values)
> +{
> +	int i, err;
> +
> +	for (i = 0; i < max_entries; i++) {
> +		keys[i] = i;
> +		values[i] = i + 1;
> +	}
> +
> +	err = bpf_map_update_batch(map_fd, keys, values, &max_entries, 0, 0);
> +	CHECK(err, "bpf_map_update_batch()", "error:%s\n", strerror(errno));
> +}
> +
> +static void map_batch_verify(int *visited, __u32 max_entries,
> +			     int *keys, int *values)
> +{
> +	int i;
> +
> +	memset(visited, 0, max_entries * sizeof(*visited));
> +	for (i = 0; i < max_entries; i++) {
> +		CHECK(keys[i] + 1 != values[i], "key/value checking",
> +		      "error: i %d key %d value %d\n", i, keys[i], values[i]);
> +		visited[i] = 1;
> +	}
> +	for (i = 0; i < max_entries; i++) {
> +		CHECK(visited[i] != 1, "visited checking",
> +		      "error: keys array at index %d missing\n", i);
> +	}
> +}
> +
> +void test_map_lookup_and_delete_batch_array(void)
> +{
> +	struct bpf_create_map_attr xattr = {
> +		.name = "array_map",
> +		.map_type = BPF_MAP_TYPE_ARRAY,
> +		.key_size = sizeof(int),
> +		.value_size = sizeof(int),
> +	};
> +	int map_fd, *keys, *values, *visited;
> +	__u32 count, total, total_success;
> +	const __u32 max_entries = 10;
> +	int err, i, step;
> +	bool nospace_err;
> +	__u64 batch = 0;
> +
> +	xattr.max_entries = max_entries;
> +	map_fd = bpf_create_map_xattr(&xattr);
> +	CHECK(map_fd == -1,
> +	      "bpf_create_map_xattr()", "error:%s\n", strerror(errno));
> +
> +	keys = malloc(max_entries * sizeof(int));
> +	values = malloc(max_entries * sizeof(int));
> +	visited = malloc(max_entries * sizeof(int));
> +	CHECK(!keys || !values || !visited, "malloc()", "error:%s\n",
> +	      strerror(errno));
> +
> +	/* populate elements to the map */
> +	map_batch_update(map_fd, max_entries, keys, values);
> +
> +	/* test 1: lookup in a loop with various steps. */
> +	total_success = 0;
> +	for (step = 1; step < max_entries; step++) {
> +		map_batch_update(map_fd, max_entries, keys, values);
> +		memset(keys, 0, max_entries * sizeof(*keys));
> +		memset(values, 0, max_entries * sizeof(*values));
> +		batch = 0;
> +		total = 0;
> +		i = 0;
> +		/* iteratively lookup/delete elements with 'step'
> +		 * elements each.
> +		 */
> +		count = step;
> +		nospace_err = false;
> +		while (true) {
> +			err = bpf_map_lookup_batch(map_fd,
> +						total ? &batch : NULL, &batch,
> +						keys + total,
> +						values + total,
> +						&count, 0, 0);
> +
> +			CHECK((err && errno != ENOENT), "lookup with steps",
> +			      "error: %s\n", strerror(errno));
> +
> +			total += count;
> +
> +			if (err)
> +				break;
> +
> +			i++;
> +		}
> +
> +		if (nospace_err == true)
> +			continue;
> +
> +		CHECK(total != max_entries, "lookup with steps",
> +		      "total = %u, max_entries = %u\n", total, max_entries);
> +
> +		map_batch_verify(visited, max_entries, keys, values);
> +
> +		total_success++;
> +	}
> +
> +	CHECK(total_success == 0, "check total_success",
> +	      "unexpected failure\n");
> +
> +	printf("%s:PASS\n", __func__);
> +}
> 

  reply	other threads:[~2019-11-21 18:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 19:30 [PATCH v2 bpf-next 0/9] add bpf batch ops to process more than 1 elem Brian Vazquez
2019-11-19 19:30 ` [PATCH v2 bpf-next 1/9] bpf: add bpf_map_{value_size,update_value,map_copy_value} functions Brian Vazquez
2019-11-22 16:36   ` John Fastabend
2019-11-19 19:30 ` [PATCH v2 bpf-next 2/9] bpf: add generic support for lookup and lookup_and_delete batch ops Brian Vazquez
2019-11-21 17:36   ` Yonghong Song
2019-11-21 21:36     ` Brian Vazquez
2019-11-22  0:34       ` Yonghong Song
2019-11-22 17:25   ` John Fastabend
2019-11-19 19:30 ` [PATCH v2 bpf-next 3/9] bpf: add generic support for update and delete " Brian Vazquez
2019-11-21 18:00   ` Yonghong Song
2019-11-22  5:50     ` Brian Vazquez
2019-11-22  6:56       ` Yonghong Song
2019-11-19 19:30 ` [PATCH v2 bpf-next 4/9] bpf: add lookup and updated batch ops to arraymap Brian Vazquez
2019-11-19 19:30 ` [PATCH v2 bpf-next 5/9] bpf: add batch ops to all htab bpf map Brian Vazquez
2019-11-21 18:27   ` Yonghong Song
2019-11-21 21:27     ` Brian Vazquez
2019-11-19 19:30 ` [PATCH v2 bpf-next 6/9] tools/bpf: sync uapi header bpf.h Brian Vazquez
2019-11-19 19:30 ` [PATCH v2 bpf-next 7/9] libbpf: add libbpf support to batch ops Brian Vazquez
2019-11-21 18:30   ` Yonghong Song
2019-11-19 19:30 ` [PATCH v2 bpf-next 8/9] selftests/bpf: add batch ops testing for hmap and hmap_percpu Brian Vazquez
2019-11-21 18:36   ` Yonghong Song
2019-11-21 21:16     ` Brian Vazquez
2019-11-19 19:30 ` [PATCH v2 bpf-next 9/9] selftests/bpf: add batch ops testing to array bpf map Brian Vazquez
2019-11-21 18:43   ` Yonghong Song [this message]
2019-11-21 21:14     ` Brian Vazquez
2019-11-22  0:22       ` Yonghong Song

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=4688ba20-0730-7689-9332-aa0dcef5258e@fb.com \
    --to=yhs@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brianvv.kernel@gmail.com \
    --cc=brianvv@google.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ppenkov@google.com \
    --cc=sdf@google.com \
    --cc=willemb@google.com \
    /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