Date: Tue, 26 Sep 2023 15:33:45 +0200 From: Kurt Jaeger <pi@freebsd.org> To: mike tancsa <mike@sentex.net> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: ifconfig -v ix0 output delay Message-ID: <20230926133345.GC81481@home.opsec.eu> In-Reply-To: <14cd1c6b-0020-4116-a3de-0b7399810bee@sentex.net> References: <dcf71d1b-7bae-4db7-bd97-9ecb7f4d8a64@sentex.net> <20230926072840.GA81481@home.opsec.eu> <14cd1c6b-0020-4116-a3de-0b7399810bee@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > > A small annoyance, but I was wondering why "ifconfig -v ix0" seems to take > > > a "long time" compared to other 10G nics. e.g. > > [...] > > > > Which version of the ix driver did you load ? The base one or > > the one from the ports, net/intel-ix-kmod ? I'm not sure > > freebsd@intel.com is reading this list, so maybe pointing > > them to the issue via some PR would be useful. > > This is just the base driver, built in ix with copper PHY I tested it with two ports on a 13.2p3 box with the port intel-ix-kmod in version 3.3.35 and the ports behave like you have observed: ix<n> NICs with SFP+ cage display the optics info, if available. ix<n> NICs with copper-port have approx. 0.4s delay. I guess that the driver should know if a certain model of the NIC has a SFP+ cage with some i2c bus -- and if it's copper-only, it should not query the bus. -- pi@opsec.eu +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230926133345.GC81481>