Date: Tue, 26 Aug 2003 12:38:58 +0800 From: David Xu <davidxu@viatech.com.cn> To: Jeff Roberson <jroberson@chesapeake.net> Cc: "freebsd-java@freebsd.org" <freebsd-java@freebsd.org> Subject: Re: vmark hangs with libthr and libkse Message-ID: <3F4AE462.3040808@viatech.com.cn> In-Reply-To: <20030826000750.N12093-100000@mail.chesapeake.net> References: <20030826000750.N12093-100000@mail.chesapeake.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson wrote: >>>> >>>> >>>Why do you need to do adjustrunqueue() in sched_prio? I also don't >>>understand the case in sched_switchout(). Can you please explain that? >>> >>> >>> >>> >>adjustrunqueue maintains kg_last_assigned and related things, when a >>thread's priority is changed, >>the thread might no longer can be in scheduler's run queue, instead it >>will be in ksegrp's runqueue, >>because there is higher priority thread, and a KSE it attached should be >>detached now, and the KSE >>will attach to another higher priority thread, ULE ignores this >>requirement, as I can understand, >>ULE is only aware of 1:1 between KSE and thread. >>It would be nice if scheduler interface is thread aware but not kse aware. >> >> > >Yes, wouldn't it be nice.. I don't think it should be ksegrp aware >either. oh well, it wasn't my design. > > SA process doesn't rely on kse and ksegrp because I introduced a kse_upcall structure, so I don't care someone drops kse or ksegrp and makes them as scheduler specific data structure. >Will you commit this patch? > > Will do.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F4AE462.3040808>