[prev in list] [next in list] [prev in thread] [next in thread] 

List:       9fans
Subject:    Re: [9fans] soverflow for fx->in
From:       James Chapman <james () cs ! ioc ! ee>
Date:       2010-07-25 9:57:37
Message-ID: AANLkTikQ-e4PQy1gk93v+JbWFn5Pj1SGLybq+dZ05yC= () mail ! gmail ! com
[Download RAW message or body]

Thanks Erik. Removing the first instance of the print in
/sys/src/9/pc/devether.c appears to fix it:

/* print("soverflow for f->in\n");  */

There is another another print lower down but I left this there for the moment.

term% time upas/fs -f /imaps/imap.gmail.com/address_removed@gmail.com

!Adding key: proto=pass server=imap.gmail.com service=imap
user=address_removed@gmail.com
password:
!
0.21u 1.04s 35.59r 	 upas/fs -f /imaps/imap.gmail.com/address_removed@gmail.com

This was for 595 messages actually.

Many thanks,

James

On Sun, Jul 25, 2010 at 7:52 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> Also, I just did a pull from sources which appears to have updated
>> almost the complete contents of /386. This caused the "soverflow for
>> fx->in" message to appear. I had to run pull three times to get it to
>> finish.
>
> maybe my first message wasn't that clear.  any ethernet activity
> can cause this if the input queue can't be drained fast enough.
> clearly, too much of the cpu is spent in interrupt context receiving
> packets, and not enough processing them. but delete the print, and
> tcp congestion avoidance should make up the difference fast enough
> to keep the remote happy.
>
> - erik
>
>


[prev in list] [next in list] [prev in thread] [next in thread]