From owner-freebsd-net@freebsd.org Fri Nov 27 20:55:22 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 76BE846899B for ; Fri, 27 Nov 2020 20:55:22 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [104.129.130.189]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CjRj620mvz4Sck for ; Fri, 27 Nov 2020 20:55:22 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5] (may be forged)) by mail.farley.org (8.16.1/8.16.1) with ESMTP id 0ARKpjUn010916; Fri, 27 Nov 2020 15:51:45 -0500 (EST) (envelope-from scf@FreeBSD.org) Date: Fri, 27 Nov 2020 15:51:45 -0500 (EST) From: "Sean C. Farley" To: "Saad, Mark" cc: Michael Sierchio , "freebsd-net@freebsd.org" Subject: Re: Determining cause of transfer limit In-Reply-To: Message-ID: <5c3242ed-d3ad-965f-5a36-c3f89cffcd58@FreeBSD.org> References: <9d7b39fb-7c1-fe7b-fa9a-ab1aa89cb96a@FreeBSD.org>, MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.0 required=4.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.farley.org X-Rspamd-Queue-Id: 4CjRj620mvz4Sck X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; ASN(0.00)[asn:396949, ipnet:104.129.130.0/24, country:US] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2020 20:55:22 -0000 On Sat, 21 Nov 2020, Saad, Mark wrote: > scf > can I use polling on sfxge ? Also if I want to use polling on say ix > or sfxge does this break things like pf, bird or nsd ? > > --- > Mark Saad > Lucera Financial Infrastructures, LLC > msaad@lucera.com I wish I could help, but I have little knowledge about the device polling capability. Did you intend to ask Michael? However, I can say that according to polling(4) man page, neither ix(4) nor sfxge(4) are listed as supported by it. I saw no change regarding pf with polling in the kernel. Finally, polling is recommended (somewhere?) for slower hardware. If you are using a 10Gb adapter, you most likely have a faster system that does not need it. You should ask in a separate E-mail thread if you have issues with that driver or hardware. Sean -- scf@FreeBSD.org > ________________________________________ > From: owner-freebsd-net@freebsd.org on behalf of Michael Sierchio > Sent: Saturday, November 21, 2020 4:55 PM > To: Sean C. Farley > Cc: freebsd-net@freebsd.org > Subject: Re: Determining cause of transfer limit > > Sorry for the top post. Have you tried device polling? From > /usr/src/sys/amd64/conf/NOTES: > options DEVICE_POLLING *snip* > On Sat, Nov 21, 2020 at 10:24 AM Sean C. Farley wrote: > >> I have recently upped my Internet service and have now noticed a limit >> being reached, but I am not certain which limit and best option to >> resolve it. *snip*