From: Frederic Weisbecker <fweisbec@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andy Lutomirski <luto@amacapital.net>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Lameter <cl@linux.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Chris Metcalf <cmetcalf@ezchip.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [Ksummit-discuss] [BELATED CORE TOPIC] context tracking / nohz / RCU state
Date: Mon, 19 Oct 2015 16:14:06 +0200 [thread overview]
Message-ID: <20151019141404.GB8952@lerouge> (raw)
In-Reply-To: <20151017194500.GC2678@thunk.org>
On Sat, Oct 17, 2015 at 03:45:00PM -0400, Theodore Ts'o wrote:
> On Fri, Oct 16, 2015 at 07:02:58PM +0200, Frederic Weisbecker wrote:
> > On Mon, Oct 12, 2015 at 01:40:05PM -0700, Paul E. McKenney wrote:
> > > On Mon, Oct 12, 2015 at 02:40:51PM -0400, Theodore Ts'o wrote:
> > > > This thread had fairly intense discussion for two days, but then went dead.
> > > >
> > > > Do folks think this is worth discussing at the kernel summit?
> > >
> > > I am very interested in discussing this. Of course, part of that
> > > interest is due to the direct involvement of RCU code.
> >
> > Please don't talk about this without me. Context tracking is deeply involved
> > and I haven't been invited to kernel summit.
>
> Are you going to be in Seoul for the Korea Linux Forum? (KLF
> attendees are welcome to attend the dual-track technical sessions
> day.)
Neither :-)
But that's fine, I'm usually not useful speaking design face to face.
I need time and editor to stare at for hours before answering.
So I'll wait for email/patches to come and either ack or nack :-)
Thanks.
prev parent reply other threads:[~2015-10-19 14:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 17:49 Andy Lutomirski
2015-08-11 18:33 ` Paul E. McKenney
2015-08-11 19:07 ` Andy Lutomirski
2015-08-11 21:47 ` Paul E. McKenney
2015-08-11 21:52 ` Andy Lutomirski
2015-08-12 0:51 ` Paul E. McKenney
2015-08-12 1:16 ` Andy Lutomirski
2015-08-12 13:38 ` Paul E. McKenney
2015-08-12 14:52 ` Frederic Weisbecker
2015-08-12 14:38 ` Frederic Weisbecker
2015-08-12 15:59 ` Paul E. McKenney
2015-08-11 18:42 ` Luis R. Rodriguez
2015-08-11 21:50 ` Paul E. McKenney
2015-08-12 20:17 ` Luis R. Rodriguez
2015-08-12 14:27 ` Frederic Weisbecker
2015-08-12 16:03 ` Paul E. McKenney
2015-08-13 1:29 ` Lai Jiangshan
2015-08-13 13:07 ` Frederic Weisbecker
2015-08-13 13:03 ` Frederic Weisbecker
2015-08-11 19:31 ` josh
2015-08-11 21:32 ` Kevin Hilman
2015-08-12 3:56 ` Lai Jiangshan
2015-08-12 14:20 ` Frederic Weisbecker
2015-10-12 18:40 ` Theodore Ts'o
2015-10-12 19:55 ` Thomas Gleixner
2015-10-12 20:40 ` Paul E. McKenney
2015-10-16 17:02 ` Frederic Weisbecker
2015-10-17 19:45 ` Theodore Ts'o
2015-10-19 14:14 ` Frederic Weisbecker [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=20151019141404.GB8952@lerouge \
--to=fweisbec@gmail.com \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=hpa@zytor.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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