All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: Dave Tucker <dave@dtucker.co.uk>
Cc: bpf@vger.kernel.org, corbet@lwn.net, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
	songliubraving@fb.com, john.fastabend@gmail.com,
	kpsingh@kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 bpf-next 2/2] bpf, docs: document BPF_MAP_TYPE_ARRAY
Date: Mon, 04 Jul 2022 11:39:53 +0100	[thread overview]
Message-ID: <m2y1x940w6.fsf@gmail.com> (raw)
In-Reply-To: <ca8a57db17da57f403b029c14ba4f0b89774d361.1656590177.git.dave@dtucker.co.uk> (Dave Tucker's message of "Thu, 30 Jun 2022 13:04:09 +0100")

Dave Tucker <dave@dtucker.co.uk> writes:

> +Since Kernel 5.4, memory mapping may be enabled for ``BPF_MAP_TYPE_ARRAY`` by

It looks to be 5.5 according to bootlin:

https://elixir.bootlin.com/linux/v5.4.203/A/ident/BPF_F_MMAPABLE
https://elixir.bootlin.com/linux/v5.5/A/ident/BPF_F_MMAPABLE

> +Array elements can also be added using the ``bpf_map_update_elem()`` helper or
> +libbpf API.
> +
> +Since the array is of constant size, ``bpf_map_delete_elem()`` is not supported.
> +To clear an array element, you may use ``bpf_map_update_eleme()`` to insert a
> +zero value to that index.

Typo in bpf_map_update_elem().

Thanks!
--
Donald Hunter

      parent reply	other threads:[~2022-07-04 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 12:04 [PATCH v4 bpf-next 0/2] bpf, docs: Document BPF_MAP_TYPE_ARRAY Dave Tucker
2022-06-30 12:04 ` [PATCH v4 bpf-next 1/2] bpf, docs: add kernel version to map_cgroup_storage Dave Tucker
2022-07-01  2:10   ` Bagas Sanjaya
2022-06-30 12:04 ` [PATCH v4 bpf-next 2/2] bpf, docs: document BPF_MAP_TYPE_ARRAY Dave Tucker
2022-06-30 13:31   ` Jonathan Corbet
2022-07-01  3:26   ` Bagas Sanjaya
2022-07-04 10:39   ` Donald Hunter [this message]

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=m2y1x940w6.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=dave@dtucker.co.uk \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=songliubraving@fb.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 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.