From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fweimer@redhat.com>
Received: from us-smtp-delivery-124.mimecast.com
 (us-smtp-delivery-124.mimecast.com [170.10.133.124])
 by sourceware.org (Postfix) with ESMTP id 43295389852E
 for <libc-help@sourceware.org>; Thu, 20 May 2021 11:02:56 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 43295389852E
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-208-EMZuoeP6OSSSIg8EBNd8eA-1; Thu, 20 May 2021 07:02:54 -0400
X-MC-Unique: EMZuoeP6OSSSIg8EBNd8eA-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com
 [10.5.11.14])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 615C41020C49;
 Thu, 20 May 2021 11:02:53 +0000 (UTC)
Received: from oldenburg.str.redhat.com (ovpn-112-137.ams2.redhat.com
 [10.36.112.137])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id 87B6E68363;
 Thu, 20 May 2021 11:02:52 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: Alexandre Bique via Libc-help <libc-help@sourceware.org>
Subject: Re: Yield to specific thread?
References: <CAP737o+pyjscAYZSjWHDvs+R6b0hJwDhY-h=G9RZk9_O8jMWXA@mail.gmail.com>
Date: Thu, 20 May 2021 13:02:50 +0200
In-Reply-To: <CAP737o+pyjscAYZSjWHDvs+R6b0hJwDhY-h=G9RZk9_O8jMWXA@mail.gmail.com>
 (Alexandre Bique via Libc-help's message of "Thu, 20 May 2021 12:42:20
 +0200")
Message-ID: <877djtsm5h.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: libc-help@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Libc-help mailing list <libc-help.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/libc-help>,
 <mailto:libc-help-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/libc-help/>
List-Help: <mailto:libc-help-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/libc-help>,
 <mailto:libc-help-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 11:02:57 -0000

* Alexandre Bique via Libc-help:

> Ideally I'd like to do:
> A produces a request
> A sched_yield_to(B)
> B processes the request
> B sched_yield_to(A)

This looks like an application for a condition variable or perhaps a
barrier.  If there is just a single writer, the kernel should wake up
the desired thread.

Thanks,
Florian