Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
* William Bloom [EMAIL PROTECTED] [2005-10-07 01:16]: then wouldn't there be more problems like mine mentioned in the lists? And I'm running into high interrupts with only about 4Mbs throughput while others have claimed much higher values. bandwidth is (almost) irrelevant. packet rates matter. -- BS Web Services, http://www.bsws.de/ OpenBSD-based Webhosting, Mail Services, Managed Servers, ... Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
On 06/10/05, Craig Barraclough [EMAIL PROTECTED] wrote: You'll find a few of us are running the interrupt holdoff patch, which IIRC, comes from the FreeBSD tree via [EMAIL PROTECTED] (See below). Patch trades off timeliness of response for reduced interrupts. Hasn't broken anything for me (yet?) on a checkout of -current as of this afternoon. Even while dragging stuff to and from the office at 720KB/s and running tor, my ssh sessions are still plenty responsive and I have a whopping 12% cpu free. Not the sort of box I'd want to run a large enterprise through, but it runs cool and quiet, takes up less room on my comms shelf than the cable modem, and has a feature set vastly superior to any other home router I've seen. -- GDB has a 'break' feature; why doesn't it have 'fix' too?
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
If the Soekris did not come with ethernet chipsets which are just slightly over the bar of rl(4), the wimpy processor in the machine might be able to cope.
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
If the Soekris did not come with ethernet chipsets which are just slightly over the bar of rl(4), the wimpy processor in the machine might be able to cope. Throughput is only marginally better using an em in the pci slot of a 4801. I think there's some other problem. Yeah -- the super wimpy processor.
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
--On 06 October 2005 16:00 -0600, Theo de Raadt wrote: If the Soekris did not come with ethernet chipsets which are just slightly over the bar of rl(4), the wimpy processor in the machine might be able to cope. Throughput is only marginally better using an em in the pci slot of a 4801. I think there's some other problem.
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
I wondered that as well, but there appear to be lots (so it appears from other postings I found using google) of 4801s in use with OpenBSD, doing essentially the same thing as myself (Soekris w/ carp/pf/pfsynch). Yet, AFAICT, I'm the only one who's posted about this symptom. Since there are lots of people who do what I do, and if the problem were indeed that the 4801 processor is too wimpy, then wouldn't there be more problems like mine mentioned in the lists? And I'm running into high interrupts with only about 4Mbs throughput while others have claimed much higher values. Before I used this firewall that I have now, I used m0n0wall on FreeBSD. I chose OpenBSD over m0n0wall/FreeBSD due to m0n0wall state table limitations and lack of mature redundance features. But the m0n0wall handled this much traffic, and more, with a relatively low interrupt mode. As widely as OpenBSD is used on Soekris for firewalling compared to m0n0wall/FreeBSD with relatively few problems, I'm still not quite ready to decide that I haven't gotten myself a setup flaw somewhere. Just can't figure out where it could be. Bill Theo de Raadt wrote: If the Soekris did not come with ethernet chipsets which are just slightly over the bar of rl(4), the wimpy processor in the machine might be able to cope. Throughput is only marginally better using an em in the pci slot of a 4801. I think there's some other problem. Yeah -- the super wimpy processor. -- William Bloom| Snr Systems Engineer|M P H A S I S Architecting Value | Eldorado Computing 5353 North 16th Street, Suite 400 Phoenix, Az 85016 | Direct: +11-602-604-3100 | Fax: +11-602-604-3115| http://www.eldocomp.com -- CONFIDENTIALITY NOTICE -- Information transmitted by this e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at [EMAIL PROTECTED] and delete this mail from your records.
Re: High Interrupt Mode Reported by 'Top' for Soekris 4801
On Fri, 7 Oct 2005 09:08, you wrote: I wondered that as well, but there appear to be lots (so it appears from other postings I found using google) of 4801s in use with OpenBSD, doing essentially the same thing as myself (Soekris w/ carp/pf/pfsynch). Yet, AFAICT, I'm the only one who's posted about this symptom. Since there are lots of people who do what I do, and if the problem were indeed that the 4801 processor is too wimpy, then wouldn't there be more problems like mine mentioned in the lists? And I'm running into high interrupts with only about 4Mbs throughput while others have claimed much higher values. Before I used this firewall that I have now, I used m0n0wall on FreeBSD. I chose OpenBSD over m0n0wall/FreeBSD due to m0n0wall state table limitations and lack of mature redundance features. But the m0n0wall handled this much traffic, and more, with a relatively low interrupt mode. As widely as OpenBSD is used on Soekris for firewalling compared to m0n0wall/FreeBSD with relatively few problems, I'm still not quite ready to decide that I haven't gotten myself a setup flaw somewhere. Just can't figure out where it could be. You'll find a few of us are running the interrupt holdoff patch, which IIRC, comes from the FreeBSD tree via [EMAIL PROTECTED] (See below). Patch trades off timeliness of response for reduced interrupts. Index: src/sys/dev/pci/if_sis.c === RCS file: /cvs/src/sys/dev/pci/if_sis.c,v retrieving revision 1.46 diff -u -r1.46 if_sis.c --- src/sys/dev/pci/if_sis.c27 May 2005 04:52:24 - 1.46 +++ src/sys/dev/pci/if_sis.c7 Jun 2005 07:14:37 - @@ -1692,6 +1692,10 @@ sis_stop(sc); sc-sis_stopped = 0; + /* Configure interrupt holdoff register. */ + if (sc-sis_type == SIS_TYPE_83815 sc-sis_srr == NS_SRR_16A) + CSR_WRITE_4(sc, NS_IHR, NS_IHR_VALUE); + mii = sc-sc_mii; /* Set MAC address */ Index: src/sys/dev/pci/if_sisreg.h === RCS file: /cvs/src/sys/dev/pci/if_sisreg.h,v retrieving revision 1.21 diff -u -r1.21 if_sisreg.h --- src/sys/dev/pci/if_sisreg.h 22 May 2005 05:40:52 - 1.21 +++ src/sys/dev/pci/if_sisreg.h 7 Jun 2005 07:14:38 - @@ -208,6 +208,20 @@ SIS_IMR_RX_IDLE|\ SIS_IMR_SYSERR) +/* Interrupt Holdoff Register */ +#define NS_IHR_HOLDCTL 0x0100 + +/* + * Interrupt holdoff value for NS DP8316. We can have the chip + * delay interrupt delivery for a certain period. Units are in + * 100us, and the default is 100us holdoff. + */ +#ifndef NS_IHR_DELAY +#define NS_IHR_DELAY 2 +#endif + +#define NS_IHR_VALUE (NS_IHR_HOLDCTL|NS_IHR_DELAY) + #define SIS_IER_INTRENB0x0001 #define SIS_PHYCTL_ACCESS 0x0010 -- Craig
