Date: Fri, 28 Mar 2014 12:44:38 -0700 From: Julian Elischer <julian@freebsd.org> To: Chris Torek <torek@mail.torek.net>, freebsd-hackers@freebsd.org, kib@freebsd.org Subject: Re: slight problem with r254457 (kthread_add fix) Message-ID: <5335D126.7040904@freebsd.org> In-Reply-To: <201403280932.s2S9W5s3073181@elf.torek.net> References: <201403280932.s2S9W5s3073181@elf.torek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/28/14, 2:32 AM, Chris Torek wrote: > (Overall, I like the "make MD code clean things up" method > better. Depending on thread0 state is pretty hacky. It's > just more work to check everything.) > > (I remember when someone, I think it may have been Mike Karels, > shuffled all the members of "struct proc" around so that we could > use the bcopy-some, bzero-some method to speed up fork(). It's > a hack too, but it's a nice one, and it's still in there, in > modified form. :-) ) yes I kept that when I made the separate thread structure. both the thread and process structures do the same thing.. > > Chris >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5335D126.7040904>