What is the interaction with intrd (PSARC/2004/199) here whose purpose is to balance interrupts across CPU's ? Does the use of this tool imply that the intrd service should be disabled (could they end up conflicting with each other) ?
Thanks pete Garrett D'Amore wrote: > > As the ARC tools seem to have "eaten" my previous posts, we're > restarting this case with a new time out one week from today (timeout > 04/22/2009). > > The project team is requesting patch binding, and volatile commitment. > This is filed on behalf of Erwin Tsaur. > > Proposal follows: > > Project Description: > PCITool was previously conceived in PSARC 2005/232, but was > intended as an internal only tool. This case would make the > command line interface, pcitool, available to external customers. > This case is open to public and contains no sun proprietary > information. > > PCITool is required to re-assign and balance interrupt loads on > multi-CPU systems. Public access to this functionality is > required if Sun wishes to claim performance advantages at system > RR. > > It will allow independent 3rd parties to verify and achieve the > posted performance numbers. Without this tool TPC-C benchmarks > for Batoka+ cannot be published > > Risks and Assumptions: > PCITool allows privileged users to remap interrupt-CPU bindings > safely. It also has the capability of accessing, including > modifying device registers in the load/store domain. Such actions > may result in a performance and functional behavior change of the > system. > > The device register access functionality will be kept > undocumented. Man page and on-line help will only mentioned > interrupt binding options. > > Technical Description: > A new package, SUNWio-tools, will be created and released to the > general public. > > Zones will be limited as defined in the pkginfo template. > SUNW_PKG_ALLZONES="true" > SUNW_PKG_HOLLOW="true" > SUNW_PKG_THISZONE="false" > > The above settings will prevent pcitool from being installed in a > non-global zone. PCITool will only work in a global zone, since > it is not possible to export nodes or the minor nodes used by > pcitool in /devices/xxx to a non-global zone. > > Bug/RFE Number(s): > 6799018 pcitool should be available as a supported tool on Solaris 10 > In Scope: > Productize PCITool through a Solaris package. > > Out of Scope: > Changing PCITool in any significant way. > Interfaces: > pcitool is an admin tool. > > pcitool <PCI nexus node> -i [ ino=<ino> ] [ -r | -w cpu=<CPU> ] [ -v ] > > -i [ ino=<ino> ] changes or retrieves current CPU for interrupts > of given nexus and optionally given ino. Ino must be selected if > -w specified. If no ino is selected (as for displaying), all > will be selected. > > -w cpu=<CPU> to change an ino<->CPU binding. > > -r for displaying ino<->CPU bindings of all selected inos on a > given nexus. All relevant enabled inos supporting non-nexus > device interrupts will be printed. For each printed ino, all > supported devices and their CPU binding will be displayed. On > some platforms, inos dedicated to the root nexus will be shown > and marked with "(Internal)". > > -v gives verbose output for all modes. > > Doc Impact: > A new PCITool manpage will be created with only the interrupt-CPU > binding options. > Reference Documents: > PSARC 2005/232 > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org