linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mtahhan@redhat.com
To: bpf@vger.kernel.org, linux-doc@vger.kernel.org
Cc: jbrouer@redhat.com, thoiland@redhat.com, donhunte@redhat.com,
	Maryam Tahhan <mtahhan@redhat.com>,
	Lorenzo Bianconi <lorenzo@kernel.org>
Subject: [PATCH bpf-next v3 0/1] docs: BPF_MAP_TYPE_CPUMAP
Date: Mon,  7 Nov 2022 11:52:06 -0500	[thread overview]
Message-ID: <20221107165207.2682075-1-mtahhan@redhat.com> (raw)

From: Maryam Tahhan <mtahhan@redhat.com>

Add documentation for BPF_MAP_TYPE_CPUMAP including
kernel version introduced, usage and examples.

Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
Co-developed-by: Lorenzo Bianconi <lorenzo@kernel.org>

v3:
- Updated introduction to use cpumap definition from kernel/bpf/cpumap.c
- Separated examples and APIs under Kernel and Userspace headings.
- Updated Userspace function signatures.
- Fixed typos.
- Migrated the use of u32 types to __u32.

v2:
- Removed TMI.
- Updated example to use a round robin scheme.

Maryam Tahhan (1):
  docs: BPF_MAP_TYPE_CPUMAP

 Documentation/bpf/map_cpumap.rst | 166 +++++++++++++++++++++++++++++++
 kernel/bpf/cpumap.c              |   9 +-
 2 files changed, 172 insertions(+), 3 deletions(-)
 create mode 100644 Documentation/bpf/map_cpumap.rst

-- 
2.35.3


             reply	other threads:[~2022-11-07 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 16:52 mtahhan [this message]
2022-11-07 16:52 ` [PATCH bpf-next v3 1/1] docs: BPF_MAP_TYPE_CPUMAP mtahhan
2022-11-07 20:17   ` Yonghong Song
2022-11-13  0:19   ` Akira Yokosawa
2022-11-11 19:29 ` [PATCH bpf-next v3 0/1] " Andrii Nakryiko
2022-11-11 19:30 ` patchwork-bot+netdevbpf

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=20221107165207.2682075-1-mtahhan@redhat.com \
    --to=mtahhan@redhat.com \
    --cc=bpf@vger.kernel.org \
    --cc=donhunte@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=thoiland@redhat.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;
as well as URLs for NNTP newsgroup(s).