richard@omnis:/home/richard$ ps -ef -o pset,class,user,group,comm |grep FX
|sort -u
- FX root root /usr/lib/zones/zonestatd
- FX daemon daemon /usr/lib/nfs/lockd
- FX daemon daemon /usr/lib/nfs/nfs4cbd
- FX daemon daemon /usr/lib/nfs/nfsd
1 FX postgres postgres /opt/local/bin/postgres
According to the "System Administration Guide: Oracle Solaris
Containers-Resource Management and Oracle Solaris Zones"
===========================
By default, the FSS scheduling class uses the same range of priorities
(0 to 59) as the timesharing (TS), interactive (IA), and fixed priority
(FX) scheduling classes. Therefore, you should avoid having processes
from these scheduling classes share the same processor set. A mix of
processes in the FSS, TS, IA, and FX classes could result in unexpected
scheduling behavior.
With the use of processor sets, you can mix TS, IA, and FX with FSS in
one system. However, all the processes that run on each processor set
must be in one scheduling class, so they do not compete for the same
CPUs. The FX scheduler in particular should not be used in conjunction
with the FSS scheduling class unless processor sets are used. This
action prevents applications in the FX class from using priorities high
enough to starve applications in the FSS class.
============================
Is there not lacking a simple means (non-dynamic) to get NFS to use
a specific project (since it uses the generic daemon user/group) in
order to be able to put it via project options into the FX processor
set by modifying the?
If not, isn't this a useful idea for the case where FSS is enabled?
Same for 'zonestatd' and others that "hardcode" the FX sched class...
-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com
