Another note: use of ndd to use /dev/hme (or whatever) without a PPA
number is pretty common for S10 systems (see -instance to set the PPA).
This is unsupported in Nevada.
-- Garrett
On 04/ 5/10 08:08 PM, Girish Moodalbail wrote:
Baban/Rishi,
Since ndd(1M) will be executed natively from within S10C, the S10
users will also not be able
to (due to CR 4616660 and Brussels II changes) modify/view following
tunables as well:
/dev/ip
ip_squeue_enter (this needs to be modified via /etc/system)
<if>:ip_forwarding
<if>:ip6_forwarding
ip_ill_status (::ill should be used)
ip_ipif_status (::ipif should be used)
ipv4_ire_status (::ire should be used)
ipv6_ire_status
ip_ndp_cache_report (::nce should be used)
ip_conn_status
ip_srcid_status
ip_rput_pullups
/dev/tcp (following info is accessed through ::netstat, CR 4616660)
tcp_bind_hash
tcp_listen_hash
tcp_acceptor_hash
tcp_conn_hash
tcp_status
/dev/udp (following info is accessed through ::netstat, CR 4616660)
udp_status
udp_bind_hash
~Girish
On 4/2/10 1:57 PM, Sebastien Roy wrote:
I'm submitting this fast-track for Baban Kenkre and Rishi Srivatsavai.
The timer is set for 04/09/2010. The release binding is Minor.
This case adds exclusive IP stack support to Solaris 10 containers.
The initial Solaris 10 container case only added support for the
shared IP stack model (see PSARC/2009/253). Adding exclusive IP stack
support involves identifying which features use user/kernel interfaces
that have changed incompatibly between Solaris 10 and now (preventing
such features from working correctly in s10c), and implementing
techniques described in the Solaris 10 Branded Zone Developer Guide[1]
to make them work. Therefore, this case doesn't introduce any new
interfaces, but simply describes the architecture introduced to make
existing features work in a Solaris 10 container.
The design document included in the materials directory [2] contains
details of how each feature that comprises exclusive IP stack support
is handled by this project. The document also enumerates features
that traditionally work in exclusive IP stacks, but that will not be
supported even after this project integrates. With the exception of
those features, a Solaris 10 branded zone should behave the same way
as a native Solaris 10 zone running on Solaris 10.
[1]
http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide
[2] materials/s10ceval.txt (relative to the case directory)
-Seb
_______________________________________________
opensolaris-arc mailing list
[email protected]
