From: Lai Jiangshan <jiangshanlai@gmail.com>
To: Chris Mason <clm@fb.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>,
Peter Zijlstra <peterz@infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jens Axboe <axboe@fb.com>, Shaohua Li <shli@fb.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] lightweight per-cpu locks / restartable sequences
Date: Wed, 22 Jul 2015 22:03:30 +0800 [thread overview]
Message-ID: <CAJhGHyA0m-LEBKMo5CgVun54zOFBpuJBU8LKyTy+-HwKZaEiPQ@mail.gmail.com> (raw)
In-Reply-To: <20150709190916.GI1522@ret.masoncoding.com>
On Fri, Jul 10, 2015 at 3:09 AM, Chris Mason <clm@fb.com> wrote:
>
> We've started experimenting with these to cut overheads in a few
> critical places, and while we don't have numbers yet I really hope it
> won't take too long.
>
> I think the topic is really interesting and we'll be able to get numbers
> from production workloads to help justify and compare different
> approaches.
>
I was interested by the idea since Paul(paulmck) and Mathieu introduced
it to me at the K.S. 2013. I didn't expect it is re-posted on LKML so late.
IMHO, the direction is useful and helpful not just only fun, I hope we can make
some progress on it.
Thanks
Lai
> -chris
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
prev parent reply other threads:[~2015-07-22 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 18:32 Andy Lutomirski
2015-07-09 19:09 ` Chris Mason
2015-07-10 17:26 ` Christoph Lameter
2015-07-13 9:57 ` Peter Zijlstra
2015-07-13 14:01 ` Christoph Lameter
2015-07-14 20:00 ` Andy Lutomirski
2015-07-14 21:15 ` Christoph Lameter
2015-07-22 14:22 ` Lai Jiangshan
2015-07-22 14:34 ` Lai Jiangshan
2015-07-22 14:03 ` Lai Jiangshan [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=CAJhGHyA0m-LEBKMo5CgVun54zOFBpuJBU8LKyTy+-HwKZaEiPQ@mail.gmail.com \
--to=jiangshanlai@gmail.com \
--cc=axboe@fb.com \
--cc=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=shli@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