Re: kern/58168: IFF_OACTIVE semantics and replacement plan is unclear

[Jason Thorpe <thorpej%me.com@localhost>]

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

From: Jason Thorpe <thorpej%me.com@localhost>
To: matthew green <mrg%eterna23.net@localhost>
Cc: kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost,
 gnats-bugs%netbsd.org@localhost
Subject: Re: kern/58168: IFF_OACTIVE semantics and replacement plan is unclear
Date: Thu, 18 Apr 2024 10:17:01 -0700

 > On Apr 17, 2024, at 11:01=E2=80=AFPM, matthew green <mrg%eterna23.net@localhost> =
 wrote:
 >=20
 > taylor pointed out that net/if.c does pay attention to this
 > flag.  it won't call if_start if it is set, assuming that
 > the device is already running the queue.
 >=20
 > that check, if needed, should also be moved into the device
 > if_start() if not already there.
 
 Good time to remind folks about the thorpej-ifq branch that specifically =
 addresses all of this stuff.  It=E2=80=99s still a W-I-P, of course, but =
 it=E2=80=99s designed to be able to co-exist with the old way as drivers =
 are transitioned.
 
 -- thorpej