Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct

From: Randy.Dunlap (rddunlap_at_osdl.org)
Date: 08/11/03

  • Next message: Robert Love: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"
    Date:	Sun, 10 Aug 2003 21:33:05 -0700 (PDT)
    To: <rml@ufl.edu>
    
    

    > On Sun, 2003-08-10 at 20:48, Randy.Dunlap wrote:
    >
    >> Yes, for most architectures, it prints interrupts from 0 thru NR_IRQS:
    >> for (i = 0 ; i < NR_IRQS ; i++)
    >> len += sprintf(page + len, " %u", kstat_irqs(i));
    >> and NR_IRQS varies depending on the kernel build options, but (for x86) is
    >> usually either 16 or 224.
    >
    > Eww. So I guess on SMP, it is 224.

    Yes.

    > Might be nice to only print lines that are registered, like
    > /proc/interrupts. But then you have no way of knowing which field is which
    > interrupt line. Ugh.
    >
    > How can we expect anything to parse that line?

    Ugh-ly? We can move it to sysfs and then change the file format
    to intnum:count pairs (e.g.).

    ~Randy

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Robert Love: "Re: /proc/stat's intr field looks odd, although /proc/interrupts seems correct"

    Relevant Pages

    • Re: 2.6.3 - Badness in pci_find_subsys at drivers/pci/search.c:167
      ... Ugh, this is due to calling system_bus_clockfrom within an interrupt. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] 3c59x: read current link status from phy
      ... there is only one interrupt that for data transmission (both Tx ... The MII registers are not ... Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: is killing zombies possible w/o a reboot?
      ... An interrupt could be received at any time, ... in uninterruptible state because it is uninterruptible ... Processes must never get stuck in D, it's a kernel bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test7-mm1
      ... >> handlers happens to start a thread, ... Problem is, things like bus resets happen in interrupt, and while I can ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: CONFIG_IRQBALANCE for AMD64?
      ... Provide some sort of cache-affinity for network interrupt processing, ... Utilize idle CPUs where possible to shoulder the load. ... I'll confess to not having looked at non-i386 arches. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)