From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <68638b4d5ce91576c9c27e434824c8be@kw.quanstro.net>
References: <AANLkTikHogzkNszF8aiU=jK1ijVwEv-Y9uk=Oh0nf5m1@mail.gmail.com>
	<68638b4d5ce91576c9c27e434824c8be@kw.quanstro.net>
Date: Sun, 25 Jul 2010 12:57:37 +0300
Message-ID: <AANLkTikQ-e4PQy1gk93v+JbWFn5Pj1SGLybq+dZ05yC=@mail.gmail.com>
From: James Chapman <james@cs.ioc.ee>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] soverflow for fx->in
Topicbox-Message-UUID: 43e35996-ead6-11e9-9d60-3106f5b1d025

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 mom=
ent.

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

!Adding key: proto=3Dpass server=3Dimap.gmail.com service=3Dimap
user=3Daddress_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> wro=
te:
>> 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. =A0any 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
>
>