[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Socket options KPI
Iain Hibbert wrote:
On Fri, 18 Jan 2008, Elad Efrat wrote:
All comments are welcome. It's not planned on being committed anytime
soon (unless, of course, all feedback suggests otherwise), so take your
time carefully reviewing the changes if you're interested. :)
Something I'm not keen on is the SOPT_SET/SOPT_GET thing. Would it be too
much work to split pr_ctloutput() into pr_setopt() and pr_getopt()?
..or would that be undesireable?
Let's do this in smaller steps so we don't break too much stuff. :)
For the first step, I'd like to reduce the mbuf abuse.
wrt this, is it known if there exists any networking code that is not
included with NetBSD that would cause problems if the KPI is evolved? (I
have a faint urge to split pr_usrreq() up into component functions also :)
I think FreeBSD already did this.
Main Index |
Thread Index |