Date: Sat, 7 Mar 2015 00:27:28 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Wei Hu <weh@microsoft.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Luigi Rizzo <rizzo@iet.unipi.it> Subject: Re: Network interrupt and NAPI in FreeBSD? Message-ID: <CAJ-Vmon3iwTyvVGdOS42G3OSRAs8bwi7NcUDonmcN64xEcwDGw@mail.gmail.com> In-Reply-To: <BY1PR0301MB09024C00FF371C7B9E57711EBB1D0@BY1PR0301MB0902.namprd03.prod.outlook.com> References: <BY1PR0301MB0902C944E2287E0C6B5D8287BB1C0@BY1PR0301MB0902.namprd03.prod.outlook.com> <CA%2BhQ2%2Bi6d_tsqKpkYVh2jnVQaS4TZ5X7zyh_54ZecQDjm%2BFkRA@mail.gmail.com> <BY1PR0301MB09024C00FF371C7B9E57711EBB1D0@BY1PR0301MB0902.namprd03.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Well, hm. What's generating the interrupts? How many interrupts/second are you talking about here? People have asked about a NAPI style solution for FreeBSD for a while, but for most folk that are using one physical interface that does interrupt moderation/rate-limiting, it turns out to not be all that big a benefit. For boxes that haves multiple interfaces, or for VMs whose software interrupt path doesn't implement any kind of thresholds for interrupt moderation, it still can be a benefit. So maybe try looking at making your driver support POLLING and see what happens. Maybe virtualisation will be the straw that breaks the NAPI back for FreeBSD. ;) -a
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon3iwTyvVGdOS42G3OSRAs8bwi7NcUDonmcN64xEcwDGw>