From: David Miller <davem@davemloft.net>
To: alexei.starovoitov@gmail.com
Cc: tglx@linutronix.de, ast@kernel.org, daniel@iogearbox.net,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: bpf and local lock
Date: Mon, 02 Dec 2019 15:08:19 -0800 (PST) [thread overview]
Message-ID: <20191202.150819.1676106400310976788.davem@davemloft.net> (raw)
In-Reply-To: <20191202215237.jz7zkriantxyclj5@ast-mbp.dhcp.thefacebook.com>
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Date: Mon, 2 Dec 2019 13:52:38 -0800
> On Mon, Nov 25, 2019 at 11:14:33AM -0800, David Miller wrote:
>>
>> Thomas,
>>
>> I am working on eliminating the explicit softirq disables around BPF
>> program invocation and replacing it with local lock usage instead.
>>
>> We would really need to at least have the non-RT stubs upstream to
>> propagate this cleanly, do you think this is possible?
>
> Hi Thomas,
>
> seconding the same question: any chance local lock api can be sent upstream
> soon? If api skeleton can get in during this merge window we will have the next
> bpf-next/net-next cycle to sort out details. If not the bpf+rt would need to
> wait one more release. Not a big deal. Just trying to figure out a time line
> when can we start working on concrete bpf+rt patches.
FWIW, I have some simple patches I'm working on that start to annotate
the bpf function invocation call sites.
And as part of that I add the non-RT stubs plus some new interfaces I
think might be necessary.
I've been told Thomas is going to be offline for another week so I'll
just keep working on this and post when I have something concrete.
prev parent reply other threads:[~2019-12-02 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:14 bpf and local lock David Miller
2019-12-02 21:52 ` Alexei Starovoitov
2019-12-02 23:08 ` David Miller [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=20191202.150819.1676106400310976788.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).