Date: Tue, 16 Apr 2013 17:52:41 +0800 From: Sepherosa Ziehau <sepherosa@gmail.com> To: Bruce Evans <brde@optusnet.com.au> Cc: YongHyeon PYUN <pyunyh@gmail.com>, Sean Bruno <sean_bruno@yahoo.com>, bde <bde@freebsd.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: bge(4) sysctl tuneables -- a blast from the past. Message-ID: <CAMOc5cy%2BG4QaV5dcPCt%2ByJE%2BmbKWApQEJ%2BAxKaZHeUukYUmrHw@mail.gmail.com> In-Reply-To: <20130416162150.X1106@besplex.bde.org> References: <1365781568.1418.1.camel@localhost> <20130413200512.G1165@besplex.bde.org> <1366065356.1350.7.camel@localhost> <20130416052500.GA1428@michelle.cdnetworks.com> <20130416162150.X1106@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 16, 2013 at 3:14 PM, Bruce Evans <brde@optusnet.com.au> wrote: > bge_rx_coal_ticks == 0 && bge_rx_max_coal_bds == 0 might work accidentally > if there are enough tx interrupts. There is also the DEVICE_POLLING > mistake. > In polling mode, these parameters of course have no effect (Polling mode > disables interrupts, and the coal parameters have no effect when interrupts > are disabled). As far as I have tested, coalesce BDs and ticks also control how often status block is updated, so it does affect polling(4) Best Regards, sephe -- Tomorrow Will Never Die
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOc5cy%2BG4QaV5dcPCt%2ByJE%2BmbKWApQEJ%2BAxKaZHeUukYUmrHw>