mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: user-space concurrent pipe buffer scheduler interactions
Date: Thu, 4 Apr 2024 15:59:36 +1300	[thread overview]
Message-ID: <719745d9-cbb6-4691-a037-2ea7fff8494a@metaparadigm.com> (raw)
In-Reply-To: <CAHk-=wiOqTAX7nwQqHJ2Ti3dbxM-HrUJq3FD_Gjua5qW=QAoTg@mail.gmail.com>

On 4/4/24 09:57, Linus Torvalds wrote:
> On Wed, 3 Apr 2024 at 13:52, Michael Clark <michael@metaparadigm.com> wrote:
>>
>> On 4/4/24 05:56, Linus Torvalds wrote:
>>> On Tue, 2 Apr 2024 at 13:54, Michael Clark <michael@metaparadigm.com> wrote:
>>>>
>>>> I am working on a low latency cross-platform concurrent pipe buffer
>>>> using C11 threads and atomics.
>>>
>>> You will never get good performance doing spinlocks in user space
>>> unless you actually tell the scheduler about the spinlocks, and have
>>> some way to actually sleep on contention.
>>>
>>> Which I don't see you as having.
>>
>> We can work on this.
> 
> It's been tried.
> 
> Nobody ever found a use-case that is sufficiently convincing, but see
> the write-up at
> 
>     https://lwn.net/Articles/944895/

It's certainly interesting!

I wouldn't throw in the towel so soon until folks tried a bit harder. 
Even if we can't make it faster it would be neat to have an Austin Group 
meeting to give us user-space devels a waitlist_t so we don't hit that 
brain damaged deadlocky cond_wait foot-gun and realize its totally 
broken and that we must use cond_timedwait with some stupid delay until 
we can recheck the condition again in user-space in our "portable code".

Michael.

  reply	other threads:[~2024-04-04  3:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 20:53 Michael Clark
2024-04-03 16:56 ` Linus Torvalds
2024-04-03 20:39   ` Michael Clark
2024-04-03 20:57     ` Linus Torvalds
2024-04-04  2:59       ` Michael Clark [this message]
2024-04-03 21:02     ` Michael Clark

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=719745d9-cbb6-4691-a037-2ea7fff8494a@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®