From owner-freebsd-net@freebsd.org  Fri Oct 26 08:12:49 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84FD010DB118
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri, 26 Oct 2018 08:12:49 +0000 (UTC)
 (envelope-from m.muenz@spam-fetish.org)
Received: from mailout-02.maxonline.de (mailout-02.maxonline.de [81.24.66.23])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 255526BEC5
 for <freebsd-net@freebsd.org>; Fri, 26 Oct 2018 08:12:48 +0000 (UTC)
 (envelope-from m.muenz@spam-fetish.org)
Received: from web03-01.max-it.de (web03-01.max-it.de [81.24.64.215])
 by mailout-02.maxonline.de (Postfix) with ESMTPS id 6096C2A6
 for <freebsd-net@freebsd.org>; Fri, 26 Oct 2018 10:12:40 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by web03-01.max-it.de (Postfix) with ESMTP id 5562A28B84C
 for <freebsd-net@freebsd.org>; Fri, 26 Oct 2018 10:12:40 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at web03-01.max-it.de
Received: from web03-01.max-it.de ([127.0.0.1])
 by localhost (web03-01.max-it.de [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id 9U_o4PZVv4Oi for <freebsd-net@freebsd.org>;
 Fri, 26 Oct 2018 10:12:40 +0200 (CEST)
Received: from [81.24.66.132] (unknown [81.24.66.132])
 (Authenticated sender: m.muenz@spam-fetish.org)
 by web03-01.max-it.de (Postfix) with ESMTPA id 2AE1E28B84A
 for <freebsd-net@freebsd.org>; Fri, 26 Oct 2018 10:12:40 +0200 (CEST)
To: freebsd-net@freebsd.org
From: "Muenz, Michael" <m.muenz@spam-fetish.org>
Subject: ipfw: PRIO scheduler
Message-ID: <c81b89ab-e8e8-edcc-36ba-3edb914077b3@spam-fetish.org>
Date: Fri, 26 Oct 2018 10:12:40 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2018 08:12:49 -0000

Hi,

On my FreeBSD system I always see :

load_dn_sched dn_sched PRIO loaded

I tried to gather some informations about this scheduler cause I never 
heard of,
but all I can find is an old thread about a kernel panic. Also no 
information via
man page, but I can successfully add a pipe with a PRIO scheduler.

Anyone here with some bits of knowledge what happened to this scheduler and
if it's for production use?

For me it sounds like a hard priority queue where everything else will 
starve
(when congested).

Thanks!
Michael