Thanks a lot to Bart! So I see there's no direct reference between ulwp_t and klwp_t, because they are managed in different spaces, and a pointer shouldn't be used to link the other. But I think one ulwp should have its corresponding klwp, since Solaris' thread model is 1-1. So I guess it is thread id that bring them together. Is that right?
2009/2/7 Bart Smaalders <bart.smaalders at sun.com> > Shu Wu wrote: > >> Hi, folks! Can anyone explain to me how ulwp_t relates to its klwp_t? By >> now I just know klwp_t and kthread_t are linked to each other, and kthread_t >> are a linked list in proc_t. And it seems ulwps are managed in uberdata. But >> I can't find in ON source how ulwp_t is related to klwp_t. Isn't there a >> direct reference between them? Thanks a lot! >> >> > klwp_t is a kernel lwp - a kernel thread that can go into userland, > receive signals, etc. > > > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/sys/klwp.h#193 > > A ulwp_t is the details of managing a thread at user level in libc. > > > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/inc/thr_uberdata.h#653 > > There really isn't a direct reference between the two. > > The only place there's much direct knowledge is through the schedctl stuff. > > > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/sys/schedctl.h#sc_shared_t > > - Bart > > > -- > Bart Smaalders Solaris Kernel Performance > barts at cyber.eng.sun.com http://blogs.sun.com/barts > "You will contribute more with mercurial than with thunderbird." > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/on-discuss/attachments/20090209/f6fd381f/attachment.html>
