From: Zebediah Figura
> Sent: 08 March 2021 16:18
>
> On 3/3/21 6:42 PM, André Almeida wrote:
> > ** The wait on multiple problem
> >
> > The use case lies in the Wine implementation of the Windows NT interface
> > WaitMultipleObjects. This Windows API function allows a thread to sleep
> >
On 3/3/21 6:42 PM, André Almeida wrote:
** The wait on multiple problem
The use case lies in the Wine implementation of the Windows NT interface
WaitMultipleObjects. This Windows API function allows a thread to sleep
waiting on the first of a set of event sources (mutexes, timers, signal
Am 08.03.21 um 12:11 schrieb David Laight:
> From: Stefan Metzmacher
>> Sent: 07 March 2021 11:35
>>
>> Hi André,
>>> ** The wait on multiple problem
>>>
>>> The use case lies in the Wine implementation of the Windows NT interface
>>> WaitMultipleObjects. This Windows API function allows a threa
Am 07.03.21 um 12:56 schrieb Daurnimator:
> On Sun, 7 Mar 2021 at 22:35, Stefan Metzmacher wrote:
>> Instead of having a blocked futex_waitv() waiting on an fd (maybe a generic
>> eventfd() or a new futex2fd())
>> would be a better interface?
>
> Like bring back FUTEX_FD? (which was removed ba
From: Stefan Metzmacher
> Sent: 07 March 2021 11:35
>
> Hi André,
> > ** The wait on multiple problem
> >
> > The use case lies in the Wine implementation of the Windows NT interface
> > WaitMultipleObjects. This Windows API function allows a thread to sleep
> > waiting on the first of a set o
On Sun, 7 Mar 2021 at 22:35, Stefan Metzmacher wrote:
> Instead of having a blocked futex_waitv() waiting on an fd (maybe a generic
> eventfd() or a new futex2fd())
> would be a better interface?
Like bring back FUTEX_FD? (which was removed back in 2.6.25)
Hi André,
> ** The wait on multiple problem
>
> The use case lies in the Wine implementation of the Windows NT interface
> WaitMultipleObjects. This Windows API function allows a thread to sleep
> waiting on the first of a set of event sources (mutexes, timers, signal,
> console input, etc)
On Fri, Mar 5, 2021 at 12:03 PM Peter Oskolkov wrote:
>
> Hi André!
>
> On Thu, Mar 4, 2021 at 10:58 AM André Almeida
> wrote:
> >
> > Hi Peter,
> >
> > Às 02:44 de 04/03/21, Peter Oskolkov escreveu:
> > > On Wed, Mar 3, 2021 at 5:22 PM André Almeida
> > > wrote:
> > >>
> > >> Hi,
> > >>
> > >
Hi André!
On Thu, Mar 4, 2021 at 10:58 AM André Almeida wrote:
>
> Hi Peter,
>
> Às 02:44 de 04/03/21, Peter Oskolkov escreveu:
> > On Wed, Mar 3, 2021 at 5:22 PM André Almeida
> > wrote:
> >>
> >> Hi,
> >>
> >> This patch series introduces the futex2 syscalls.
> >>
> >> * FAQ
> >>
> >> ** "A
Hi Ted,
Às 12:01 de 04/03/21, Theodore Ts'o escreveu:
On Wed, Mar 03, 2021 at 09:42:06PM -0300, André Almeida wrote:
** Performance
- For comparing futex() and futex2() performance, I used the artificial
benchmarks implemented at perf (wake, wake-parallel, hash and
requeue). The se
Hi Peter,
Às 02:44 de 04/03/21, Peter Oskolkov escreveu:
On Wed, Mar 3, 2021 at 5:22 PM André Almeida wrote:
Hi,
This patch series introduces the futex2 syscalls.
* FAQ
** "And what's about FUTEX_64?"
By supporting 64 bit futexes, the kernel structure for futex would
need to have a
On Wed, Mar 03, 2021 at 09:42:06PM -0300, André Almeida wrote:
> ** Performance
>
> - For comparing futex() and futex2() performance, I used the artificial
>benchmarks implemented at perf (wake, wake-parallel, hash and
>requeue). The setup was 200 runs for each test and using 8, 80, 800,
On Wed, Mar 3, 2021 at 5:22 PM André Almeida wrote:
>
> Hi,
>
> This patch series introduces the futex2 syscalls.
>
> * What happened to the current futex()?
>
> For some years now, developers have been trying to add new features to
> futex, but maintainers have been reluctant to accept then, give
13 matches
Mail list logo
