[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mtspm7fe.fsf@meer.lwn.net>
Date: Thu, 20 May 2021 15:17:25 -0600
From: Jonathan Corbet <corbet@....net>
To: Peter Oskolkov <posk@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org
Cc: Paul Turner <pjt@...gle.com>, Ben Segall <bsegall@...gle.com>,
Peter Oskolkov <posk@...gle.com>,
Peter Oskolkov <posk@...k.io>,
Joel Fernandes <joel@...lfernandes.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrei Vagin <avagin@...gle.com>,
Jim Newsome <jnewsome@...project.org>
Subject: Re: [RFC PATCH v0.1 0/9] UMCG early preview/RFC patchset
Peter Oskolkov <posk@...gle.com> writes:
> As indicated earlier in the FUTEX_SWAP patchset:
>
> https://lore.kernel.org/lkml/20200722234538.166697-1-posk@posk.io/
>
> "Google Fibers" is a userspace scheduling framework
> used widely and successfully at Google to improve in-process workload
> isolation and response latencies. We are working on open-sourcing
> this framework, and UMCG (User-Managed Concurrency Groups) kernel
> patches are intended as the foundation of this.
So I have to ask...is there *any* documentation out there on what this
is and how people are supposed to use it? Shockingly, typing "Google
fibers" into Google leads to a less than fully joyful outcome... This
won't be easy for anybody to review if they have to start by
reverse-engineering what it's supposed to do.
Thanks,
jon
Powered by blists - more mailing lists