From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60268 invoked by alias); 14 Jun 2018 14:01:29 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 57262 invoked by uid 89); 14 Jun 2018 14:00:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=painful X-HELO: mx1.redhat.com Subject: Re: Restartable Sequences system call merged into Linux To: Pavel Machek , Mathieu Desnoyers Cc: carlos , Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , Thomas Gleixner , linux-kernel , libc-alpha References: <1084280721.10859.1528746558696.JavaMail.zimbra@efficios.com> <31fc101a-295b-067b-1a82-7e9e509fc92f@redhat.com> <305409897.10888.1528747473727.JavaMail.zimbra@efficios.com> <091061df-3482-8762-30e4-feaf3417be11@redhat.com> <417742741.11550.1528821084084.JavaMail.zimbra@efficios.com> <20180614122759.GB8798@amd> <894222691.12973.1528981314012.JavaMail.zimbra@efficios.com> <20180614132557.GA15201@amd> <956816108.13001.1528983496098.JavaMail.zimbra@efficios.com> <20180614134959.GA4084@amd> From: Florian Weimer Message-ID: <48a0d905-2568-51b8-80c9-a20ecaa25f9b@redhat.com> Date: Thu, 14 Jun 2018 14:01:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180614134959.GA4084@amd> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-06/txt/msg00411.txt.bz2 On 06/14/2018 03:49 PM, Pavel Machek wrote: > Hi! > >>>> - rseq_preempt(): on preemption, the scheduler sets the TIF_NOTIFY_RESUME thread >>>> flag, so rseq_handle_notify_resume() can check whether it's in a rseq critical >>>> section when returning to user-space, >>>> - rseq_signal_deliver(): on signal delivery, rseq_handle_notify_resume() checks >>>> whether it's in a rseq critical section, >>>> - rseq_migrate: on migration, the scheduler sets TIF_NOTIFY_RESUME as well, >>> >>> Yes, this is not likely to be noticeable. >>> >>> But the proposal wanted to add a syscall to thread creation, right? >>> And I believe that may be noticeable. >> >> Fair point! Do we have a standard benchmark that would stress this ? > > Web server performance benchmarks basically test clone() performance > in many cases. Isn't that fork? I expect that the rseq arena is inherited on fork and fork-type clone, otherwise it's going to be painful. Thanks, Florian