Date: Fri, 1 Jul 2005 15:11:40 +0100 From: Peter Edwards <peadar.edwards@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: Peter Edwards <peadar@freebsd.org>, arch@freebsd.org Subject: Re: ktrace and KTR_DROP Message-ID: <34cb7c8405070107112ac9de26@mail.gmail.com> In-Reply-To: <200507011005.21343.jhb@FreeBSD.org> References: <20050701132104.GA95135@freefall.freebsd.org> <200507011005.21343.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/1/05, John Baldwin <jhb@freebsd.org> wrote: > On Friday 01 July 2005 09:21 am, Peter Edwards wrote: > > Y'all, > > > > Ever since the introduction of a separate ktrace worker thread for > > writing output, there's the distinct possibility that ktrace output > > will drop requests. For some proceses, it's actually inevitable: > > as long as the traced processes can sustain a rate of generating > > ktrace events faster than the ktrace thread can write them, you'll > > eventually run out of ktrace requests. >=20 > The patch looks good to me, and I'd even be ok with having neverdrop on b= y > default. FWIW, that would also be my preference, I was just being conservative.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34cb7c8405070107112ac9de26>