From nobody Tue Apr 18 22:19:30 2023 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Q1JHx5h0vz45lsF; Tue, 18 Apr 2023 22:19:41 +0000 (UTC) (envelope-from freebsd@igalic.co) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1JHw6WJ7z3rxX; Tue, 18 Apr 2023 22:19:40 +0000 (UTC) (envelope-from freebsd@igalic.co) Authentication-Results: mx1.freebsd.org; none Date: Tue, 18 Apr 2023 22:19:30 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=igalic.co; s=protonmail; t=1681856377; x=1682115577; bh=1rUd5nx8okNNtm5Hg5ICpC9uB9F19tzz+GsEGQSqT2o=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=WHkAWQr16VlPv2EA54zLR7auBWmCu3BrUfU06ZbDOokOO7LGF3aGhCaar33xipoQQ Rf3aj8yjugdNp6lcXcn6+Gpsbl7w3QtWyYo1SxP0vaQV7qkpEkyGNg4osZXd7/l3tL +hOPM+OCi2Y+PGZPmWePViXjvq+n5dWP1lOA8nE+fBxG8zRRaXq58DWVtoKt4t+0vX aTlhbJrff0yDFzcc9ZU35Oo1ZJWLTYcrtfo57Ggvc2W5hjitIDDJzsn4VQDq9ZcKT5 p6oLVa6/t3zxALBXx0kSH0r2lghVOxs1/ajse0sqRmBv1XziV4GOsyqrAQJoUUbETz e00pb4SYV8lbA== To: Hans Petter Selasky From: =?utf-8?Q?Mina_Gali=C4=87?= Cc: freebsd-net@freebsd.org, freebsd-infiniband@FreeBSD.org Subject: Re: Ifconfig limitations Message-ID: In-Reply-To: <2c7b7432-f7ae-67e0-87a4-e556a26d981b@selasky.org> References: <2c7b7432-f7ae-67e0-87a4-e556a26d981b@selasky.org> Feedback-ID: 66573723:user:proton List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q1JHw6WJ7z3rxX X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 4/18/23 11:44, Mina Gali=C4=87 wrote: >=20 > > Hi HPS, > >=20 > > i don't see those sysctl entries for regular devices? > > is this infiniband specific? > > or is there anything I need to enable to get these sysctls? > >=20 > > Kind regards, >=20 >=20 > Hi, Hi > The sysctl entries you are referring to are created by ibcore.ko . > Unless the network card attaches to those API's > like mlx5ib, no such entries exist. Do you know how the sysctl entries interact with renaming an interface? I know that the dev. hierarchy is perfectly ignorant of renames. > In upstream FreeBSD there is no software infiniband or RoCE support. I'm not sure I know what that means. (aside from being quite ignorant of In= finiband and its modes) Does that mean that only special vendor supplied drivers and or software wo= uld expose that functionality? > --HPS Kind regards, Mina