Re: [PATCH hurd] libpager: use a fixed number of threads

2014-11-03 Thread Ludovic Courtès
Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > Quoting Samuel Thibault (2014-11-02 13:52:16) >> AIUI, this does work because you had previously separated disk and file >> pagers? > > Yes. > >> > + /* What follows is basically the second part of >> > + mach_msg_server_timeou

Re: [PATCH hurd] libpager: use a fixed number of threads

2014-11-03 Thread Samuel Thibault
Justus Winter, le Mon 03 Nov 2014 12:23:27 +0100, a écrit : > > > + /* What follows is basically the second part of > > > + mach_msg_server_timeout. */ > > > > So you need to copy the copyright years :) > > That's not straight forward as the glibc uses year ranges (1993-2014 > in this

Re: [PATCH hurd] libpager: use a fixed number of threads

2014-11-03 Thread Justus Winter
Hi :) Quoting Samuel Thibault (2014-11-02 13:52:16) > AIUI, this does work because you had previously separated disk and file > pagers? Yes. > > + /* What follows is basically the second part of > > + mach_msg_server_timeout. */ > > So you need to copy the copyright years :) That's

Re: [PATCH hurd] libpager: use a fixed number of threads

2014-11-02 Thread Samuel Thibault
Hello, I'm thrilled by the potential of this change :D AIUI, this does work because you had previously separated disk and file pagers? Justus Winter, le Tue 28 Oct 2014 01:37:44 +0100, a écrit : > +/* Start the worker threads libpager uses to service requests. */ > +error_t > +pager_start_worke

[PATCH hurd] libpager: use a fixed number of threads

2014-10-27 Thread Justus Winter
Previously, libpager used an unbounded number of threads to receive messages from the pager bucket. It used sequence barriers to execute the requests to order requests to each object. The sequence barriers are implemented in seqnos.c. A server function uses _pager_wait_for_seqno to wait for its