On 04/23/10 10:09 AM, Darren J Moffat wrote:
2. Device visibility
...
Within each zone, lofiadm(1m) is only allowed to see, or modify,
the nodes it has created. The global zone can access all nodes,
however, for example:
# lofiadm
Block Device File Options
/dev/lofi/1 /rpool/zones/ozone/root/var/lofi/lofi_file_736429_44 -
...
If the path cannot be resolved from the global zone (for example,
it may reside on an NGZ-mounted NFS path), the File column displays
"?".
When a zone is shut down, all its lofi devices (and any mounts on
top) are unmapped and destroyed.
As today, only root users may access and modify lofi devices.
It wasn't made explicit above, so I'll ask: Can the global zone modify
non-global zone nodes in addition to being able to see them via lofiadm?
3. Resource limits
Currently, lofi has a limit of 128 devices.
Out of curiosity, why does it currently have this limit?
This case removes this
limit as it is not extendable to the multi-zone case. Instead, the
number of lofi devices is restricted by each device's associated
taskq: the lofi taskq is created as zsched thread, and the zone
resource control max-lwps applies.
Are there resources other than threads consumed? More specifically,
would there be a need for one to limit the number of lofi devices while
not limiting the number of lwps for other purposes?
-Seb
_______________________________________________
opensolaris-arc mailing list
[email protected]
