That post is most likely the hotplug PCI-Express ppb problem, I would expect that particular user's problem to be improved by changes to interrupt handling in -current. (and to head off the next question, these changes are not suitable to be backported to stable.)
On 2011-05-11, Amit Kulkarni <[email protected]> wrote: > On Wed, May 11, 2011 at 8:47 AM, Tom Murphy <[email protected]> wrote: >> I had set up ALTQ on a 4.9 firewall box as a box in our network needed >> its sending throttled, but I noticed that while the firewall was >> throttling this machine in question, ALL connections going through the >> machine were adversely affected and slow. Interactive SSH sessions had >> sometimes 1-2 seconds up to 10 seconds before keystrokes showed up. >> >> Once the machine had stopped sending all its traffic, things were fine >> again. >> >> I am not sure if the hotplug ppb and em(4) / bge(4) issue of shared >> interrupts could be applied here or not. The box happily forwards >> traffic without lag if I turn ALTQ off on it. However, this is not >> an option as we cannot go past 100 megabits on our connection. >> >> I also noticed I had to jack qlimit up to 8000 to stop getting lots of >> packets being dropped. >> >> Machine is a Dell PowerEdge R210. It's running amd64. I tried i386 on it >> and it was unstable, so switched it to amd64. >> >> Yes, it has ipmi enabled, but ipmi does not appear to cause any issues. >> It's only when ALTQ is enabled. >> >> Any ideas? Would this stuff be fixed in -current? I'd try -current on >> it, but need to convince management. >> >> Thanks, >> Tom >> >> The altq line in /etc/pf.conf: >> >> altq on em0 priq bandwidth 95Mb qlimit 8000 queue { bulk, std, mail, >> ssh, web, vpn, dns, ack } >> > > http://marc.info/?l=openbsd-misc&m=129371647818083&w=2 > > ?
