Re: EAGAIN in "read jobs pipe"

2007-01-10 Thread Howard Chu
james coleman wrote: not much! also a build making more calls to make can result in jfactor * number of make calls jobs Only if you're using a totally braindead implementation of make. The whole point of the jobserver pipe is to eliminate this fanout problem. So I might regularily use

Re: EAGAIN in "read jobs pipe"

2007-01-10 Thread Paul Smith
On Wed, 2007-01-10 at 01:53 -0800, Howard Chu wrote: > An essential design choice. This stuff relies on reads and writes of the > job_fd being atomic and the writes never blocking. POSIX guarantees a 4K > buffer for pipes. Perhaps the code should check the resource limit and > complain if the -

Re: EAGAIN in "read jobs pipe"

2007-01-10 Thread james coleman
Oh dear. Sorry people. I was of course being a bit silly when talking about make -j 16385! Howard Chu wrote: [EMAIL PROTECTED] wrote: Perhaps... On the other hand, if you're using -j 65K, why not just -j? Does you build even have 65K jobs? of course I do not use -j65k ! :-O :-) Very good

Re: EAGAIN in "read jobs pipe"

2007-01-10 Thread Howard Chu
[EMAIL PROTECTED] wrote: Noticed something else. Something else completely pointless! must not be > 16385 True, if you have 16 KB pipes... gmake -j 16386; # or above hang gmake -j 16385; # or below fire along rapidly Because you're trying to write more into the job tokens

RE: EAGAIN in "read jobs pipe"

2007-01-10 Thread lasse.makholm
>Noticed something else. > >Something else completely pointless! > > must not be > 16385 True, if you have 16 KB pipes... > gmake -j 16386; # or above hang > gmake -j 16385; # or below fire along rapidly Because you're trying to write more into the job tokens pipe than it can hold... You app

Re: EAGAIN in "read jobs pipe"

2007-01-09 Thread James Coleman
Paul Smith wrote: On Tue, 2007-01-09 at 10:32 +, James Coleman wrote: Ken Takusagawa wrote: For reasons I haven't completely triaged yet, I've been having my parallel makes die with "read jobs pipe: Resource temporarily unavailable. Stop." All memory on machine might be used up (real memo

Re: EAGAIN in "read jobs pipe"

2007-01-09 Thread Paul Smith
On Tue, 2007-01-09 at 10:32 +, James Coleman wrote: > Ken Takusagawa wrote: > > For reasons I haven't completely triaged yet, I've been having my > > parallel makes die with > > "read jobs pipe: Resource temporarily unavailable. Stop." > > All memory on machine might be used up (real memory +

Re: EAGAIN in "read jobs pipe"

2007-01-09 Thread James Coleman
Ken Takusagawa wrote: For reasons I haven't completely triaged yet, I've been having my parallel makes die with "read jobs pipe: Resource temporarily unavailable. Stop." All memory on machine might be used up (real memory + all swap). e.g. we get this: virtual memory exhausted: Resource temp