From owner-freebsd-net@FreeBSD.ORG Wed Feb 8 10:50:11 2012 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EF91106566C for ; Wed, 8 Feb 2012 10:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A16D8FC08 for ; Wed, 8 Feb 2012 10:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q18AoBIR042113 for ; Wed, 8 Feb 2012 10:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q18AoBwY042112; Wed, 8 Feb 2012 10:50:11 GMT (envelope-from gnats) Date: Wed, 8 Feb 2012 10:50:11 GMT Message-Id: <201202081050.q18AoBwY042112@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Dmitrij Tejblum Cc: Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing high CPU load for ntpd X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dmitrij Tejblum List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 10:50:11 -0000 The following reply was made to PR kern/161899; it has been noted by GNATS. From: Dmitrij Tejblum To: bug-followup@freebsd.org Cc: Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing high CPU load for ntpd Date: Wed, 08 Feb 2012 14:30:51 +0400 I would suggest to remove RTM_MISS messages at all. I believe that there is no sofware that actually use it. OTOH, in some cases RTM_MISS messages are really disturbing. E.g., a router without default route (e.g. runnung BGP) will always generate some amount of RTM_MISS messages. They have no use, but require daemons to parse them, and could result in overflow on routing socket queue and, in turn, cause some important routing messages to be dropped. I have a patch that add a sysctl to turn off RTM_MISS messages, but since no one use them, it would be easier to just remove them entirely. -- Dmitry