Re: BIRD 1.x/2.x support at rpki-client

On Mon, 02 Mar 2020, Theo de Raadt wrote: > Can't we assume bird1 will go away eventually? Yes, sooner or later. Likely later for OpenBSD when looking to net/bird/1 and net/bird/2 co-existence, thus ongoing BIRD 1.x compatibility might be more important for OpenBSD than for rpki-client downstreams

Re: fix ldapd/ldapctl data directory handling

I don't agree with this diff, even though you're right with it being broken. Right now the regress test uses it/tries to use it and even though someone trying to run regress on an actual production machine somewhat deserves to get shot in the foot, I don't think we should make that our goal. Also,

Re: ldapd: fix return values for illegal passwords

I agree that returning Operations Error is the wrong return value. I don't agree that we should *always* return invalidCredentials, however, acting like the other LDAP servers on an invalid entry seems reasonable to me. One option I do see is if we can't create an imsg to the parent process handlin

Re: net80211: use QoS frames for A-MPDUs only

On Tue, 03 Mar 2020, Stefan Sperling wrote: > Long story short: If you can test the diff below on iwn(4) (n, not m), > on a WPA2 network in 11n mode, then please do. > > ... > Since I currently don't have any iwn(4) hardware with me I would appreciate > if someone could test this diff with iwn(4)

Re: em(4) hw setup vs queues

On 3.3.2020. 11:37, Martin Pieuchot wrote: > Currently em_hw_init() uses some hardcorded values to configure TX > rings. Diff below convert it to use the value of the first queue. > This is currently a no-op. It makes the code consistent with the > rest of the driver and reduce the size of upcomi

Re: net80211: use QoS frames for A-MPDUs only

On Tue 03/03/2020 11:06, Stefan Sperling wrote: > Since I currently don't have any iwn(4) hardware with me I would appreciate > if someone could test this diff with iwn(4) in 11n mode. > Just checking whether an 11n wifi connection on a WPA2 network still works > is good enough for testing this. Th

com(4) at pci

Hi, I would like to use the serial ports on the Apollo Lake machine on my desk. My first attempt was adjusting puc(4), but then I realized that this would bloat puc(4) too much. Intel has been removing legacy I/O-Ports on recent machines. I think that started with the Skylake PCH, which added t

Initialize percpu subsystem earlier

percpu_init() should be called before cpu_configure() if we want to use per-CPU memory allocation in drivers. I placed it early, right before mbinit() because it is only initializing a memory pool and we should allow other subsystems to rely on it. Ok? Index: kern/init_main.c ===

em(4) hw setup vs queues

Currently em_hw_init() uses some hardcorded values to configure TX rings. Diff below convert it to use the value of the first queue. This is currently a no-op. It makes the code consistent with the rest of the driver and reduce the size of upcoming diffs. Note that even if a single queue is curr

net80211: use QoS frames for A-MPDUs only

Long story short: If you can test the diff below on iwn(4) (n, not m), on a WPA2 network in 11n mode, then please do. QoS wifi frames are generally used for two different things: traffic prioritization, and A-MPDU frame aggregation. Actual QoS is all about traffic prioritization, e.g. for lower