linux-kernel - Re: [patch 14/22] pollfs: pollable futex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 May 2007 10:10:22 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Davi Arnaut" <davi@...ent.com.br>
Cc:	"Eric Dumazet" <dada1@...mosbay.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Davide Libenzi" <davidel@...ilserver.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [patch 14/22] pollfs: pollable futex

On 5/2/07, Davi Arnaut <davi@...ent.com.br> wrote:
> thread A:
>     int fd = plfutex(addr, 0);
>     do
>         poll(fdset+fd);
>         process network events
>         queue obj to thread B
>         if fd:
>             job processed
>
> thread B:
>     wait_job();
>     process_job();
>     raise_event(addr);

This is not the model you can implement with your changes.  Because
every single waiter is woken you need one thread listening for the
jobs and then distribute the work.  Otherwise you have thundering
herds of threads and only one gets to do some work.

> It simple as is, there is no need to overdesign.

There is no reason to go with a limited, too-simple minded design if
we've already identified a much better design.  The fact that poll is
used today does not excuse piling on more and more code which makes
additional functions which don't fit into the poll framework barely
work.  Plus, poll/epoll itself is a problem.

And you cannot talk about little changes and no "overdesign".  You
have 22 patches for all this.  It's not just limited to futexes, it's
the whole thing which IMO is unnecessary ballast going forward.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/