Alan Altmark wrote: >It might, however, be an interesting idea to make the ioctl()s in the >device driver a no-op instead of not being present or generating its own >errnos. That way folks can turn the knob, feel better, but not see any >change since "it doesn't get any better than this".
I like the general idea, although I'm not sure I like the specifics. Here's what Jingmin Zhai wrote, for reference: >We stopped the 'irqbalance' service first, then >echo <hexadecimal bit mask> > /proc/irq/<irq vector>/smp_affinity >But get >"echo: write error: Input/output error" I suppose that's not a helpful error message, but it's echo that's generating the message. However, no-op'ing (accepting basically anything from echo and doing nothing) doesn't seem entirely satisfying either. How about a "no-op" plus a log message -- "I heard you, but I took no action because I'm already optimized for this thoroughly virtualized platform"? -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM Z and LinuxONE, AP/GCG/MEA E-Mail: [email protected] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
