Re: kern/58124 (lagg(4) fails to work with lacp protocol on mcx(4))

[Andrius V <vezhlys%gmail.com@localhost>]

The following reply was made to PR kern/58124; it has been noted by GNATS.

From: Andrius V <vezhlys%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: yamaguchi%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
	riastradh%netbsd.org@localhost
Subject: Re: kern/58124 (lagg(4) fails to work with lacp protocol on mcx(4))
Date: Fri, 19 Apr 2024 10:05:40 +0300

 On Fri, Apr 19, 2024 at 5:39=E2=80=AFAM <riastradh%netbsd.org@localhost> wrote:
 >
 > Synopsis: lagg(4) fails to work with lacp protocol on mcx(4)
 >
 > State-Changed-From-To: pending-pullups->closed
 > State-Changed-By: riastradh%NetBSD.org@localhost
 > State-Changed-When: Fri, 19 Apr 2024 02:39:52 +0000
 > State-Changed-Why:
 > fixed and pulled up to 10
 > inapplicable <10 because lagg(4) is new in 10
 >
 
 Technically speaking this ended up to be a mcx(4) issue, which may be
 relevant for NetBSD 9.
 I didn't do PR for the few reasons:
 NetBSD 9 driver is older and would need separate testing, maybe it
 would make more sense to sync the driver fully instead, it there's a
 need.
 I also didn't test if full-duplex helps agr(4), which may be an option
 for 9-th release.
 I am not planning to use it on netbsd 9.
 
 So, unless requested by someone, I am not planning to cater netbsd-9 releas=
 e.