Date: Thu, 21 May 2009 17:17:02 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "M. Warner Losh" <imp@bsdimp.com> Cc: scottl@samsco.org, src-committers@FreeBSD.org, jhb@FreeBSD.org, svn-src-all@FreeBSD.org, attilio@FreeBSD.org, svn-src-head@FreeBSD.org, rwatson@FreeBSD.org, kostikbel@gmail.com Subject: Re: svn commit: r192535 - head/sys/kern Message-ID: <2070.1242926222@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 21 May 2009 10:15:37 CST." <20090521.101537.864824728.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20090521.101537.864824728.imp@bsdimp.com>, "M. Warner Losh" writes: >Right now, the devctl_notify() is what gets it into devd. However, >I'd always viewed devd as having multiple event sources and not just >from the /dev/devctl device. Correct, but kqueuing /dev is not nearly as expressiv as devctl, where the protocol has space where the device driver could pass useful information to devd(8). For instance, I find the regexp matching of ethernet drivers very, very silly: the device driver should just tell devd(8) that it is an ethernet, so that we don't have this non-documented registry of device driver names. Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2070.1242926222>