All of lore.kernel.org
 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,
	yhs@meta.com, "Toke Høiland-Jørgensen" <toke@redhat.com>,
	"Yonghong Song" <yhs@fb.com>
Subject: Re: [PATCH bpf-next v8 1/1] doc: DEVMAPs and XDP_REDIRECT
Date: Fri, 11 Nov 2022 10:28:18 +0700	[thread overview]
Message-ID: <Y23BUlmDrRgPCapY@debian.me> (raw)
In-Reply-To: <20221110160818.1053910-2-mtahhan@redhat.com>

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

On Thu, Nov 10, 2022 at 11:08:18AM -0500, mtahhan@redhat.com wrote:
> From: Maryam Tahhan <mtahhan@redhat.com>
> 
> Add documentation for BPF_MAP_TYPE_DEVMAP and
> BPF_MAP_TYPE_DEVMAP_HASH including kernel version
> introduced, usage and examples.
> 
> Add documentation that describes XDP_REDIRECT.

Shouldn't two documentations be separated into its own patch (thus
creating 2-patch series)?

 
> +XDP_REDIRECT works with the following map types:
> +
><snipped>...
> +Silent packet drops for ``XDP_REDIRECT`` can be debugged using:
> +
> +- bpf_trace
> +- perf_record

XDP_REDIRECT is inline-quoted here, but plain on other places. I would
like to keep that above plain instead.

What about below instead?

```
Silent packet drops for ``XDP_REDIRECT`` can be debugged using either
bpf_trace tool or ``perf record`` command.
```

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-11-11  3:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 16:08 [PATCH bpf-next v8 0/1] doc: DEVMAPs and XDP_REDIRECT mtahhan
2022-11-10 16:08 ` [PATCH bpf-next v8 1/1] " mtahhan
2022-11-11  3:28   ` Bagas Sanjaya [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=Y23BUlmDrRgPCapY@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=donhunte@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=mtahhan@redhat.com \
    --cc=thoiland@redhat.com \
    --cc=toke@redhat.com \
    --cc=yhs@fb.com \
    --cc=yhs@meta.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.