Re: Periodic rant about SCHED_ULE

From: Steve Kargl <sgk_at_troutmask.apl.washington.edu>
Date: Sat, 25 Mar 2023 19:55:28 UTC
On Sat, Mar 25, 2023 at 08:08:11PM +0100, Peter wrote:
> On Sat, Mar 25, 2023 at 10:54:17AM -0700, Steve Kargl wrote:
> ! On Sat, Mar 25, 2023 at 04:47:42PM +0100, Peter wrote:
> ! > ---------------------------------------------------------------------
> ! > >> On 3/22/23, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
> ! > >>>
> ! > >>> I reported the issue with ULE some 15 to 20 years ago.
> ! > 
> ! > Can I get the PR number, please?
> ! > 
> ! 
> ! Don't remember if I ever files a bug report.
> 
> Too bad. A bugreport has the advantage that one can attach fixes
> to it, and that things get a lot more focused.

If you follow the URLs I posted to the mailing lists and
read the threads associated with those URLs, you'll find
I was in direct contact with the individual who designed
and implemented ULE.  A bug report in 2008 would have 
sat for years unless I closed it, which I have done with
other bug reports I've submitted over the years.   

> ! There's one
> ! here that was simply closed.
> ! 
> ! https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=85820
> 
> Hm, that is not really suitable.

You can re-open a bug report and enshrine your patch.
Or, you can create your own bug report with your 
analysis of the problem, and then enshrine your patch.

-- 
Steve