From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Magnus Karlsson <magnus.karlsson@intel.com>
Cc: "Björn Töpel" <bjorn.topel@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Network Development" <netdev@vger.kernel.org>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf v3] xsk: improve documentation for AF_XDP
Date: Wed, 23 Oct 2019 10:16:42 -0700 [thread overview]
Message-ID: <CAADnVQKMJX1eADxgK8ixmUd7XFKOOjdhbCybFcLCLEaUXUSuAw@mail.gmail.com> (raw)
In-Reply-To: <1571648224-16889-1-git-send-email-magnus.karlsson@intel.com>
On Mon, Oct 21, 2019 at 1:57 AM Magnus Karlsson
<magnus.karlsson@intel.com> wrote:
>
> Added sections on all the bind flags, libbpf, all the setsockopts and
> all the getsockopts. Also updated the document to reflect the latest
> features and to correct some spelling errors.
>
> v1 -> v2:
> * Updated XDP program with latest BTF map format
> * Added one more FAQ entry
> * Some minor edits and corrections
>
> v2 -> v3:
> * Simplified XDP_SHARED_UMEM example XDP program
>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
..
> + struct xdp_statistics {
> + __u64 rx_dropped; /* Dropped for reasons other than invalid desc */
> + __u64 rx_invalid_descs; /* Dropped due to invalid descriptor */
> + __u64 tx_invalid_descs; /* Dropped due to invalid descriptor */
> + };
there was small space/tab damage in the above.
I fixed it up and applied to bpf-next.
Sounds like there could be tweaks to this doc in this release cycle
when you follow up with btf and libbpf additions.
prev parent reply other threads:[~2019-10-23 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 8:57 [PATCH bpf v3] xsk: improve documentation for AF_XDP Magnus Karlsson
2019-10-23 17:16 ` Alexei Starovoitov [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=CAADnVQKMJX1eADxgK8ixmUd7XFKOOjdhbCybFcLCLEaUXUSuAw@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
/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).