All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <daniel@bristot.me>
To: Tiejun Chen <tiejunc@vmware.com>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Real-time micro-conference proposal for Linux Plumbers 2019
Date: Thu, 9 May 2019 09:56:25 +0200	[thread overview]
Message-ID: <02b2eb1e-b88b-3ade-1e0d-741bf92939b1@bristot.me> (raw)
In-Reply-To: <BYAPR05MB5878261BB896A489AA521A65C5320@BYAPR05MB5878.namprd05.prod.outlook.com>

Hi Tiejun!

On 5/8/19 6:37 AM, Tiejun Chen wrote:
> Hi Daniel,
> 
> I hope we can discuss if-how Preempt-RT kernel can be tuned to benefit container/docker. It would involve any potential new interfaces, tools/utilities, etc, and how to make Preempt-RT work very well with some Linux secure features.  Actually I tried to discuss this last year but for some reasons I did attend real-time micro-conference 2018, unfortunately. I hope we can have such a topic and I'd like to work on that as well.

Yeah, this is a hot topic! Are you planning to attend to Plumber this year? If
so, would you mind to prepare 3 or 4 slides introducing the problem to "warm-up"
the discussion at the MC?

Thanks!

-- Daniel

> 
> Thanks
> Tiejun

  reply	other threads:[~2019-05-09  7:56 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 [this message]
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
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=02b2eb1e-b88b-3ade-1e0d-741bf92939b1@bristot.me \
    --to=daniel@bristot.me \
    --cc=bristot@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tiejunc@vmware.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 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.