Date: Wed, 27 May 2009 14:30:08 +0800 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-xen@freebsd.org Subject: netfront changes (was Re: i386/134926: FreeBSD-current Xen DomU networking panic - out of tx mbufs?) Message-ID: <d763ac660905262330j1db0bd87t4162af0043b4243d@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
G'day, I've committed some sanity checking code to the FreeBSD-current/Xen netfront drivers. The driver now ensures there are TX mbuf and xen TX ring descriptor slots available before it queues a packet. There's some debugging printf()'s that will spit out messages when things go awry, eg: xn_start_locked: xn_tx_chain_cnt (254) + nfrags 2 >= NET_TX_RING_SIZE (256); must be full! xn_start_locked: xn_tx_chain_cnt (255) + nfrags 1 >= NET_TX_RING_SIZE (256); must be full! This seems to have ceased the panics under CPU/memory pressure on my playpen server. I'm going to continue tidying up the netfront driver a little more over the next few days to hopefully wrap up some dangling loose ends which I can see. I'd appreciate it if people could give FreeBSD-current/Xen a right royal thrashing (eg, 4 FreeBSD vms on one host pegging network and CPU traffic at maximum between each other) to try and elicit any other crazy network behaviour. There's only so much I can test atm. Thanks, Adrian Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d763ac660905262330j1db0bd87t4162af0043b4243d>