Date: Mon, 14 Aug 2006 13:30:37 -0700 From: "Matt Reimer" <mattjreimer@gmail.com> To: "Pyun YongHyeon" <yongari@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/em if_em.c if_em.h Message-ID: <f383264b0608141330p5ca124b8y6c4f2034a4b3eac4@mail.gmail.com> In-Reply-To: <200608140150.k7E1osuf005683@repoman.freebsd.org> References: <200608140150.k7E1osuf005683@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/13/06, Pyun YongHyeon <yongari@freebsd.org> wrote: > yongari 2006-08-14 01:50:54 UTC > > FreeBSD src repository > > Modified files: > sys/dev/em if_em.c if_em.h > Log: > Overhaul Rx path to recover from mbuf cluster allocation failure. > o Create one more spare DMA map for Rx handler to recover from > bus_dmamap_load_mbuf_sg(9) failure. > o Make sure to update status bit in Rx descriptors even if we failed > to allocate a new buffer. Previously it resulted in stuck condition > and em_handle_rxtx task took up all available CPU cycles. [snip] Is it possible that the RELENG_4 if_em driver would suffer from the same problems, particularly the stuck/CPU-chewing problem? Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f383264b0608141330p5ca124b8y6c4f2034a4b3eac4>