Re: Get PCI resources from ACPI

dmesg diff, followed by full dmesg with 2nd patch applied. No panic, at least in the time it took to grab the dmesg and reboot. Devin 1c1 < OpenBSD 5.9-beta (GENERIC.MP) #10: Fri Jan 8 09:00:37 MST 2016 --- OpenBSD 5.9-beta (GENERIC.MP) #11: Fri Jan 8 10:37:00 MST 2016 18c18 < cpu0:

Re: Putting more consistency on SYNOPSIS in section 5

2016-01-07 19:12 GMT+03:00 Ingo Schwarze : > Hi Vadim, > > Vadim Zhukov wrote on Wed, Jan 06, 2016 at 04:41:13PM +0300: > >> While mdoc(7) says that section 5 manuals do not need SYNOPSIS usually, >> we have 34 pages that do: > [...] > >> Two of those contain some complicated

Re: rework em(4) tx ring handling

On 8.1.2016. 6:18, David Gwynne wrote: > i found em_txeof hard to read, so i did this. > > i was originally going to follow myx/re and use a separate prod/cons > for a ring of packet info which would point into the descriptor > ring, but came to the conclusion that the "end of packet" pointer >

Re: rework em(4) tx ring handling

Hi, I've been hitting on the diff with iperf and ifconfig up/down cycles. It didn't trigger any watchdog issues (though I've never seen any on this box soo take it with a grain of salt). As Hrvoje said, the box is smoother under high load.. I'll continue hitting it and I'll give the diff a

fusefs uiomove() conversion

Below the conversion from uiovmovei() to uiomove() for miscfs/fusefs/. All size parameters already are size_t, so the diff is straightforward. Index: miscfs/fuse/fuse_device.c === RCS file: /cvs/src/sys/miscfs/fuse/fuse_device.c,v