Date: Fri, 06 Jan 2017 23:32:44 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 215836] [PATCH] sbin/dmesg: support new flag for watching messages Message-ID: <bug-215836-8-vCino47fYj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-215836-8@https.bugs.freebsd.org/bugzilla/> References: <bug-215836-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215836 --- Comment #4 from joe@thrallingpenguin.com --- Thank you for your feedback. I cannot simply go through syslog, as too much delay and overhead. I am proposing three solutions to this. Which sounds the most likely to suc= ceed in being accepted? 1. In researching "sys/kern/subr_log.c", I see it only accepts a single pro= cess watching (as you've kindly mentioned). Since the whole point of this file is centered around read-only operations; I feel it would be safe and fairly non-complex to support multiple processes performing open() and kevent() ca= lls by switching to a linked list of "struct selinfo". Each waiting process may then utilize kevent() mechanisms; with additional changes to the mutex call= s. 2. Use the value of "kern.log_wakeups_per_second" to calculate a better sle= ep() call between loops. 3. Keep the dmesg change locally. I am willing to accept any of these options, with #3 being done, #2 being v= ery simple, and #1 being a bit involved, but supporting a number of ideas I hav= e. Thoughts, suggestions, or ideas are welcomed! -Joe --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-215836-8-vCino47fYj>