Paul Brook wrote:
[snip]
int slirp_can_output(void)
{
-return 1;
+qemu_can_send_packet(slirp_vc);
}
It would be wise to return the value here.
- Filip
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listin
On Tue, Dec 20, 2005 at 09:14:09PM +, Paul Brook wrote:
> On Tuesday 20 December 2005 20:56, Juergen Lock wrote:
> > On Sun, Dec 18, 2005 at 11:28:27PM +, Paul Brook wrote:
> > > Teaching the slirp code how to do tcp backoff/window scaling is probably
> > > a fair amount of work. The easy
On Tuesday 20 December 2005 20:56, Juergen Lock wrote:
> On Sun, Dec 18, 2005 at 11:28:27PM +, Paul Brook wrote:
> > Teaching the slirp code how to do tcp backoff/window scaling is probably
> > a fair amount of work. The easy alternative is to throttle the slirp
> > output when we know the car
On Sun, Dec 18, 2005 at 11:28:27PM +, Paul Brook wrote:
> Dan mentioned he was seeing very poor network performance when using
> user-net.
> It turns out this is because packets were getting dropped (the NIC buffers
> were full), and the slirp code doesn't throttle properly when this occurs
Dan mentioned he was seeing very poor network performance when using user-net.
It turns out this is because packets were getting dropped (the NIC buffers
were full), and the slirp code doesn't throttle properly when this occurs.
You end up with a bunch of packets getting sent to the guest, half
