On 2020-03-02, Lauri Tirkkonen wrote:
> Thanks for the input, and ping - is there still something about this
> diff that I should fix?
I'm kinda busy, but I should be able to look into it eventually.
On Mon, Feb 24 2020 15:33:35 -0500, Ted Unangst wrote:
> Martin Pieuchot wrote:
> > On 24/02/20(Mon) 11:29, Lauri Tirkkonen wrote:
> > > On Mon, Feb 24 2020 10:24:53 +0100, Martin Pieuchot wrote:
> > > > On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> > > > > I was working on a make jobserver impl
Martin Pieuchot wrote:
> On 24/02/20(Mon) 11:29, Lauri Tirkkonen wrote:
> > On Mon, Feb 24 2020 10:24:53 +0100, Martin Pieuchot wrote:
> > > On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> > > > I was working on a make jobserver implementation that uses POSIX
> > > > semaphores as job tokens inste
On Mon, Feb 24 2020 10:42:22 +0100, Martin Pieuchot wrote:
> > Yes, that's what I'm trying to do. Yes, I've seen the current
> > implementation -- that's why I started this thread, in an attempt to
> > make them supported. :)
> >
> > See the followup patch -- sharing the semaphore between processe
On Mon, Feb 24 2020 10:42:22 +0100, Martin Pieuchot wrote:
> On 24/02/20(Mon) 11:29, Lauri Tirkkonen wrote:
> > On Mon, Feb 24 2020 10:24:53 +0100, Martin Pieuchot wrote:
> > > On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> > > > I was working on a make jobserver implementation that uses POSIX
>
On 24/02/20(Mon) 11:29, Lauri Tirkkonen wrote:
> On Mon, Feb 24 2020 10:24:53 +0100, Martin Pieuchot wrote:
> > On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> > > I was working on a make jobserver implementation that uses POSIX
> > > semaphores as job tokens instead of a complicated socket-based
On Mon, Feb 24 2020 10:24:53 +0100, Martin Pieuchot wrote:
> On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> > I was working on a make jobserver implementation that uses POSIX
> > semaphores as job tokens instead of a complicated socket-based approach.
> > Initially I used named semaphores, which
On 23/02/20(Sun) 14:48, Lauri Tirkkonen wrote:
> I was working on a make jobserver implementation that uses POSIX
> semaphores as job tokens instead of a complicated socket-based approach.
> Initially I used named semaphores, which work fine, except if child
> processes with less privileges need to
On Sun, Feb 23 2020 14:48:36 +0200, Lauri Tirkkonen wrote:
> So, diff below makes struct __sem non-opaque and removes the indirect
> allocations, so that the application is required to provide storage and
> can therefore control where it's stored (which could be eg. shm).
followup diff that makes
I was working on a make jobserver implementation that uses POSIX
semaphores as job tokens instead of a complicated socket-based approach.
Initially I used named semaphores, which work fine, except if child
processes with less privileges need to also open the named semaphore
(eg. 'make build' as roo
10 matches
Mail list logo