Date: Wed, 13 Aug 2008 21:41:03 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Mike Tancsa <mike@sentex.net> Cc: stable@FreeBSD.org Subject: Re: HEADS UP: inpcb/inpcbinfo rwlocking: coming to a 7-STABLE branch near you Message-ID: <alpine.BSF.1.10.0808132138170.41778@fledge.watson.org> In-Reply-To: <200808132034.m7DKY7wm038972@lava.sentex.ca> References: <alpine.BSF.1.10.0808031142550.65130@fledge.watson.org> <alpine.BSF.1.10.0808082219360.16028@fledge.watson.org> <200808120059.m7C0xvUH028011@lava.sentex.ca> <alpine.BSF.1.10.0808121119040.86332@fledge.watson.org> <200808132034.m7DKY7wm038972@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 13 Aug 2008, Mike Tancsa wrote: > At 06:20 AM 8/12/2008, Robert Watson wrote: > >> Anyone out there running name servers, NFS over UDP, and other UDP >> workloads: your testing of this patch prior to commit would be much >> appreciated. > > Not sure if this is related or not, but I am seeing a 'boatload' of strange > proxy arp issues. Odd thing is that I dont have proxy arp enabled anywhere, > at least not knowingly. Dear Mike: Well, it shouldn't be related, but sometimes things get tricky with locking if it turns out that extra locking at one layer was masking a lack of locking at another. Let's try to diagnose this one a bit more before concluding that is the case, though. I take that the same problems don't happen if you boot a vanilla version of the same rev of the kernel? What command did you use to generate the list at the bottom of your e-mail? Robert N M Watson Computer Laboratory University of Cambridge > > 0[smtp2]# sysctl -a | grep prox > net.link.ether.inet.proxyall: 0 > 0[smtp2]# > > > 0[smtp2]# arp -na | wc > 27665 227053 1669734 > 0[smtp2]# > > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 [ethernet] > ? (199.212.134.1) at (incomplete) on em0 published (proxy only) [ethernet] > ? (199.212.134.2) at 00:30:48:8f:3e:8a on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 published (proxy only) [ethernet] > ? (199.212.134.2) at (incomplete) on em0 published (proxy only) [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 published (proxy only) [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] > ? (199.212.134.2) at (incomplete) on em0 [ethernet] >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0808132138170.41778>