From: "Toke Høiland-Jørgensen" <toke@redhat•com>
To: John Fastabend <john.fastabend@gmail•com>,
bjorn.topel@gmail•com, bpf@vger•kernel.org,
toshiaki.makita1@gmail•com
Cc: netdev@vger•kernel.org, john.fastabend@gmail•com, ast@kernel•org,
daniel@iogearbox•net
Subject: Re: [bpf-next PATCH v2 1/2] bpf: xdp, update devmap comments to reflect napi/rcu usage
Date: Sun, 12 Jan 2020 12:21:56 +0100 [thread overview]
Message-ID: <87pnfox6ln.fsf@toke.dk> (raw)
In-Reply-To: <157879664156.8200.4955971883120344808.stgit@john-Precision-5820-Tower>
John Fastabend <john.fastabend@gmail•com> writes:
> Now that we rely on synchronize_rcu and call_rcu waiting to
> exit perempt-disable regions (NAPI) lets update the comments
> to reflect this.
>
> Fixes: 0536b85239b84 ("xdp: Simplify devmap cleanup")
> Acked-by: Björn Töpel <bjorn.topel@intel•com>
> Acked-by: Song Liu <songliubraving@fb•com>
> Signed-off-by: John Fastabend <john.fastabend@gmail•com>
Acked-by: Toke Høiland-Jørgensen <toke@redhat•com>
next prev parent reply other threads:[~2020-01-12 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 2:36 [bpf-next PATCH v2 0/2] xdp devmap improvements cleanup John Fastabend
2020-01-12 2:37 ` [bpf-next PATCH v2 1/2] bpf: xdp, update devmap comments to reflect napi/rcu usage John Fastabend
2020-01-12 7:47 ` Maciej Fijalkowski
2020-01-14 3:27 ` John Fastabend
2020-01-12 11:21 ` Toke Høiland-Jørgensen [this message]
2020-01-12 2:37 ` [bpf-next PATCH v2 2/2] bpf: xdp, remove no longer required rcu_read_{un}lock() John Fastabend
2020-01-12 6:49 ` Maciej Fijalkowski
2020-01-14 3:25 ` John Fastabend
2020-01-14 0:31 ` Maciej Fijalkowski
2020-01-12 11:22 ` Toke Høiland-Jørgensen
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=87pnfox6ln.fsf@toke.dk \
--to=toke@redhat$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=bjorn.topel@gmail$(echo .)com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=toshiaki.makita1@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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