Date: Tue, 2 Jul 2002 22:56:58 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: KSE signal problems still Message-ID: <15650.26618.523781.562050@grasshopper.cs.duke.edu> In-Reply-To: <Pine.BSF.4.21.0207021927590.97650-100000@InterJet.elischer.org> References: <15650.23048.273299.232384@grasshopper.cs.duke.edu> <Pine.BSF.4.21.0207021927590.97650-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer writes: > > > > However, it does seem a bit silly, as we end up dropping > > and-reaquiring the sched lock quite a few times: > > That's why I just asked you to test the concept.. > If I know that just aquiring it here is ok, > (I presume you tried doing some work like this) > that tells me that this code isn't called from some odd place, > with the sched lock already set. > > (that and code inspection of course..) > > Now we know it works we can try optimise it.. > > I'm going home now for dinner, > so if you feel like checking this or something mor optimal in, > be my guest :-) OK, I've checked in the unoptimized fix. Please do optimize it when you get a chance. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15650.26618.523781.562050>