On 8/25/05, Steve Shockley <[EMAIL PROTECTED]> wrote: > I've got a 3.7 box running under VMware 2.5.1. This box acts as a "hub" > for Unison (over SSH), and the data is stored on a SNAP server mounted via > NFS (not my choice). > > Originally, using the le driver, network performance was abysmal, and I > was getting a lot of collisions. > > I noticed that "le at pci" has been replaced by pcn in -current, so for > kicks I backported the driver to 3.7. (I hate chasing -current on a > production box.)
If you really want to use the old le driver, just disable pcn using the config command, and your kernel will fall back to the old le driver. However I find pcn works much better for me, so I suggest you use it, it's as easy as creating a hardlink for hostname.pcn0 to hostname.le1 (pci le always grabbed 1 or higher, 0 was isa). I leave both files there, because if I need to go back to openbsd that's pre pcn driver, then it'll use le again. > > Now, performance is reasonable, but I'm still getting collisions. A > sample from systat ifstat: > > Interfaces Ibytes Ipkts Ierrs Obytes Opkts Oerrs > Colls > pcn0 11585832 8255 0 247940 1476 0 > 368 > > Is this normal and/or acceptable? I've tried forcing full duplex on the > nic, but it doesn't seem to have any effect. > If you have other boxes on the same subnet, see what stats they are getting, I don't seem to have many problems with pcn. Jason
