Date: Tue, 20 Aug 2002 08:35:15 -0700 From: Alfred Perlstein <bright@mu.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Bruce Evans <bde@zeta.org.au>, Ian Dowse <iedowse@maths.tcd.ie>, arch@FreeBSD.ORG Subject: Re: Solving the stack gap issue Message-ID: <20020820153515.GL75574@elvis.mu.org> In-Reply-To: <15714.17605.575558.398279@grasshopper.cs.duke.edu> References: <200208171918.aa72556@salmon.maths.tcd.ie> <20020818055951.N12475-100000@gamplex.bde.org> <15714.17605.575558.398279@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
* Andrew Gallatin <gallatin@cs.duke.edu> [020820 06:32] wrote: > > For example, why do we check MPSAFE and conditionally grab and release > GIANT in syscall instead of just grabbing/releasing it in the syscall > itself? A few thousand instructions worth of bloat might be worth 2 > compares in the critical path.. Also, if the copyin fails, why do we > not just set the ret value and jump past the call, rather than setting > error and doing an extra compare a few lines later? Grunt work that just needs to be done. I can take a shot at it if no one else is currently. -- -Alfred Perlstein [alfred@freebsd.org] [#bsdcode/efnet/irc.prison.net] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020820153515.GL75574>