From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0701220854o14267e7eoa5e5812a57512794@mail.gmail.com>
Date: Mon, 22 Jan 2007 11:54:40 -0500
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] snoopy oddity
In-Reply-To: <0a8e33b5f18b75d5b68a543259e8a0ad@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <0a8e33b5f18b75d5b68a543259e8a0ad@coraid.com>
Topicbox-Message-UUID: 080526b0-ead2-11e9-9d60-3106f5b1d025

> has anyone seen snoopy miss packets like this?  i see the ack for a packet
> that snoopy never sees.  these hosts are connected back-to-back.

sure.  if snoopy isn't reading packets out of the kernel fast enough,
it will miss some.  the kernel can't buffer them up indefinitely.

for the size of the buffer:

if you are reading from a snoop file then see
/sys/src/9/ip/ipifc.c:319 (arg to qopen).

if you are reading from an ether device then see
/sys/src/9/pc/devether.c:428,440 (arg to netifinit)

russ