linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: mtahhan@redhat.com
Cc: bpf@vger.kernel.org, linux-doc@vger.kernel.org,
	jbrouer@redhat.com, thoiland@redhat.com, donhunte@redhat.com,
	john.fastabend@gmail.com
Subject: Re: [PATCH bpf-next v2 1/1] docs: BPF_MAP_TYPE_SOCK[MAP|HASH]
Date: Fri, 2 Dec 2022 09:07:16 +0700	[thread overview]
Message-ID: <Y4ld1BsRrXaPtz0L@debian.me> (raw)
In-Reply-To: <20221201151352.34810-1-mtahhan@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

On Thu, Dec 01, 2022 at 03:13:52PM +0000, mtahhan@redhat.com wrote:
> +When these maps are created BPF programs are attached to them. The list of
> +allowed programs is shown below:

Automatically attached BPF programs?

Also, "The allowed programs are:"

> +.. note::
> +	For more details of the socket callbacks that get replaced please see:
> +
> +	- TCP BPF functions: ``net/ipv4/tcp_bpf.c``
> +	- UDP BPF functions: ``net/ipv4/udp_bpf.c``

"... please see ``net/ipv4/tcp_bpf.c`` and ``net/ipv4/udp_bpf.c`` for
TCP and UDP functions, respectively"

Otherwise LGTM.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-12-02  2:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 15:13 [PATCH bpf-next v2 1/1] docs: BPF_MAP_TYPE_SOCK[MAP|HASH] mtahhan
2022-12-02  2:07 ` Bagas Sanjaya [this message]
2022-12-02  9:54   ` Maryam Tahhan
2022-12-03 19:43 ` 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=Y4ld1BsRrXaPtz0L@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=donhunte@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=mtahhan@redhat.com \
    --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).