From: Daniel Borkmann <daniel@iogearbox.net>
To: Yonghong Song <yhs@fb.com>,
Matteo Croce <mcroce@linux.microsoft.com>,
bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf-next v2] bpf: update bpf_get_smp_processor_id() documentation
Date: Wed, 15 Sep 2021 22:43:56 +0200 [thread overview]
Message-ID: <a14362ef-eceb-b5ea-0b1c-3be37d2d9a3d@iogearbox.net> (raw)
In-Reply-To: <94b5dd50-ac04-de03-996b-899f7c19a6da@fb.com>
On 9/15/21 2:07 AM, Yonghong Song wrote:
> On 9/14/21 4:54 PM, Matteo Croce wrote:
>> From: Matteo Croce <mcroce@microsoft.com>
>>
>> BPF programs run with migration disabled regardless of preemption, as
>> they are protected by migrate_disable().
>> Update the documentation accordingly.
>>
>> Signed-off-by: Matteo Croce <mcroce@microsoft.com>
>
> Acked-by: Yonghong Song <yhs@fb.com>
Applied, thanks & also copied this over to the tools/include/uapi/linux/bpf.h .
prev parent reply other threads:[~2021-09-15 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 23:54 [PATCH bpf-next v2] bpf: update bpf_get_smp_processor_id() documentation Matteo Croce
2021-09-15 0:07 ` Yonghong Song
2021-09-15 20:43 ` Daniel Borkmann [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=a14362ef-eceb-b5ea-0b1c-3be37d2d9a3d@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcroce@linux.microsoft.com \
--cc=yhs@fb.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