From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Daniel Bristot de Oliveira <daniel@bristot.me>
Cc: Daniel Bristot de Oliveira <bristot@redhat.com>,
linux-rt-users@vger.kernel.org, dhaval.giani@oracle.com,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Real-time micro-conference proposal for Linux Plumbers 2019
Date: Tue, 21 May 2019 22:05:23 -0300 [thread overview]
Message-ID: <20190522010523.GO8945@kernel.org> (raw)
In-Reply-To: <d0d44fb3-ac4a-c0c4-a9ce-76736ca70e31@bristot.me>
Em Tue, May 21, 2019 at 03:07:54PM +0200, Daniel Bristot de Oliveira escreveu:
>
>
> On 5/3/19 8:53 AM, Daniel Bristot de Oliveira wrote:
> > Hi all!
> >
>
> Hi all!
>
> Good news from OSPM!
>
> I just talked to Frederic Weisbecker, and he is proposing talking about the
> softirq rework that we need - as a step to the -rt merge!
>
> Dhaval Giani is also mentioning the possibility of talking about their needs
> w.r.t proxy execution!
>
> Anyone else with a good idea? stable-rt people??? :-)
Has anyone thought about how BPF interacts with CONFIG_PREEMPT_RT_FULL?
- Arnaldo
next prev parent reply other threads:[~2019-05-22 1:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 6:53 Real-time micro-conference proposal for Linux Plumbers 2019 Daniel Bristot de Oliveira
2019-05-06 18:43 ` Sean V Kelley
2019-05-07 6:46 ` Stéphane Ancelot
2019-05-09 7:44 ` Daniel Bristot de Oliveira
2019-05-08 4:37 ` Tiejun Chen
2019-05-09 7:56 ` Daniel Bristot de Oliveira
2019-05-14 13:26 ` Tiejun Chen
2019-05-14 20:10 ` Daniel Bristot de Oliveira
2019-06-13 2:57 ` Tiejun Chen
2019-06-13 6:36 ` Daniel Bristot de Oliveira
2019-05-21 13:07 ` Daniel Bristot de Oliveira
2019-05-22 1:05 ` Arnaldo Carvalho de Melo [this message]
2019-05-22 11:43 ` Daniel Bristot de Oliveira
2019-05-22 13:42 ` Daniel Bristot de Oliveira
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=20190522010523.GO8945@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=bristot@redhat.com \
--cc=daniel@bristot.me \
--cc=dhaval.giani@oracle.com \
--cc=fweisbec@gmail.com \
--cc=linux-rt-users@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 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.