[lkml]   [2018]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH for 4.18 12/23] cpu_opv: Provide cpu_opv system call (v7)
On Mon, Apr 16, 2018 at 12:21 PM, Mathieu Desnoyers
<> wrote:
> And I try very hard to avoid being told I'm the one breaking
> user-space. ;-)

You *can't* be breaking user space. User space doesn't use this yet.

That's actually why I'd like to start with the minimal set - to make
sure we don't introduce features that will come back to bite us later.

The one compelling use case I saw was a memory allocator that used
this for getting per-CPU (vs per-thread) memory scaling.

That code didn't need the cpu_opv system call at all.

And if somebody does a ldload of a malloc library, and then wants to
analyze the behavior of a program, maybe they should ldload their own
malloc routines first? That's pretty much par for the course for those
kinds of projects.

So I'd much rather we first merge the non-contentious parts that
actually have some numbers for "this improves performance and makes a
nice fancy malloc possible".

As it is, the cpu_opv seems to be all about theory, not about actual need.


 \ /
  Last update: 2018-04-16 21:27    [W:0.059 / U:3.528 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site