> On Nov 9, 2014, at 2:21 PM, erik quanstrom wrote:
>
> On Sun Nov 9 14:51:37 EST 2014, j...@corpus-callosum.com wrote:
>>
>>> On Nov 9, 2014, at 1:42 PM, erik quanstrom wrote:
>>>
>>> the aside leads me to believe that there is something wrong with the segment
>>> copy on fork. since the s
i can't get it to fail:
$ boom -n 1000 -c 100 http://rpi.9netics.com
1000 / 1000 Booo!
100.00 %
Summary:
Total: 26.6064 secs.
Slowest: 4.0497 secs.
Fastest: 1.1270 secs.
Average: 2.6087 secs.
Requests/sec: 37.5474
Total Data Received
On Sun Nov 9 14:51:37 EST 2014, j...@corpus-callosum.com wrote:
>
> > On Nov 9, 2014, at 1:42 PM, erik quanstrom wrote:
> >
> > the aside leads me to believe that there is something wrong with the segment
> > copy on fork. since the semaphore in question is in the data segment,
> > i'm going t
> On Nov 9, 2014, at 1:42 PM, erik quanstrom wrote:
>
> the aside leads me to believe that there is something wrong with the segment
> copy on fork. since the semaphore in question is in the data segment,
> i'm going to guess that you're running the labs kernel, and you're hitting the
> page ca
On Sun Nov 9 10:35:34 EST 2014, j...@corpus-callosum.com wrote:
> Has anyone else seen the arm httpd lock up on them? I can start it, but then
> after a few proper responses it just sits:
>
> bootes 950:00 0:00 1436K Semacqui httpd
(aside: i notice that throttle doesn't wor
Has anyone else seen the arm httpd lock up on them? I can start it, but then
after a few proper responses it just sits:
bootes 950:00 0:00 1436K Semacqui httpd
dreamplug% acid 95
/proc/95/text:arm plan 9 executable
/sys/lib/acid/port
/sys/lib/acid/arm
acid: stk()
semacquire(
On Mon Nov 18 06:46:22 EST 2013, 9f...@hamnavoe.com wrote:
> > this is because wakeup() takes about 100-1000x as long as sleep(0)
>
> [Citation needed]
since rendezvous has to do a bunch of locks and a context switch,
whereas sleep(0) doesn't really have to do anything other than
check anyhigher()
> this is because wakeup() takes about 100-1000x as long as sleep(0)
[Citation needed]
On Sun Nov 17 17:32:22 EST 2013, j...@corpus-callosum.com wrote:
> Has anyone else experienced new builds of the sources arm tree getting hung
> up with semacquire?
>
> 99: httpd pc cac0 dbgpc cac0 Semacquire (Wakeme) ut 1 st 2 bss
> 168000 qpc 608157d8 nl 0 nd 0 lpc 608758c4 pri 1
Not that this should mattter, this host is listening to 4 addresses on the IP
stack.
Don't know if this helps at all but I did an arm build a few weeks ago
and its all working fine.
-Steve
Has anyone else experienced new builds of the sources arm tree getting hung up
with semacquire?
99: httpd pc cac0 dbgpc cac0 Semacquire (Wakeme) ut 1 st 2 bss
168000 qpc 608157d8 nl 0 nd 0 lpc 608758c4 pri 10
acid: lstk()
semacquire()+0xc /sys/src/libc/9syscall/semacquire.s:6
lo
12 matches
Mail list logo
