Re: usb(4): use cacheable buffers for data transfers (massive speedup)

On Wed, Apr 01, 2020 at 12:58:23PM +1100, Jonathan Gray wrote: > On Wed, Mar 18, 2020 at 01:41:06PM +0100, Patrick Wildt wrote: > > On Wed, Mar 18, 2020 at 11:22:40AM +0100, Patrick Wildt wrote: > > > Hi, > > > > > > I've spent a few days investigating why USB ethernet adapters are so > > >

Re: usb(4): use cacheable buffers for data transfers (massive speedup)

On Wed, Mar 18, 2020 at 01:41:06PM +0100, Patrick Wildt wrote: > On Wed, Mar 18, 2020 at 11:22:40AM +0100, Patrick Wildt wrote: > > Hi, > > > > I've spent a few days investigating why USB ethernet adapters are so > > horribly slow on my ARMs. Using dt(4) I realized that it was spending > > most

Re: Prevent memory corruption by pipex_timer()

On Tue, Mar 31, 2020 at 06:15:46PM +0200, Martin Pieuchot wrote: > On 31/03/20(Tue) 18:58, Vitaliy Makkoveev wrote: > > On Tue, Mar 31, 2020 at 05:23:46PM +0200, Martin Pieuchot wrote: > > > On 31/03/20(Tue) 16:48, Vitaliy Makkoveev wrote: > > > > I refactored pppx(4). The idea is to use pipex(4)

Re: Prevent memory corruption by pipex_timer()

On 31/03/20(Tue) 18:58, Vitaliy Makkoveev wrote: > On Tue, Mar 31, 2020 at 05:23:46PM +0200, Martin Pieuchot wrote: > > On 31/03/20(Tue) 16:48, Vitaliy Makkoveev wrote: > > > I refactored pppx(4). The idea is to use pipex(4) as it was designed. > > > No one holds pipex_session outside pipex(4) so

Re: Prevent memory corruption by pipex_timer()

On Tue, Mar 31, 2020 at 05:23:46PM +0200, Martin Pieuchot wrote: > On 31/03/20(Tue) 16:48, Vitaliy Makkoveev wrote: > > I refactored pppx(4). The idea is to use pipex(4) as it was designed. > > No one holds pipex_session outside pipex(4) so pipex_timer() calls are > > safe. Unfortunately, this way

Re: Prevent memory corruption by pipex_timer()

On 31/03/20(Tue) 16:48, Vitaliy Makkoveev wrote: > I refactored pppx(4). The idea is to use pipex(4) as it was designed. > No one holds pipex_session outside pipex(4) so pipex_timer() calls are > safe. Unfortunately, this way gives some performance impact, because we > need to call

Re: Prevent memory corruption by pipex_timer()

I refactored pppx(4). The idea is to use pipex(4) as it was designed. No one holds pipex_session outside pipex(4) so pipex_timer() calls are safe. Unfortunately, this way gives some performance impact, because we need to call pipex_lookup_by_session_id() in some places. This impact will gone after

Re: PATCH: configurable tiling in cwm(1)

On Fri 2020.03.27 at 00:30 +, Uwe Werler wrote: > Hello @tech, > > with this diff https://marc.info/?l=openbsd-tech=149192690925713=2 the > behaviour of cwm changed so vtile and htile always use 50% of the screen. > > This is a reasonable default but sometimes I want to have the master

[patch] sys/queue.h

Hi there! This changes the comment in sys/queue.h a little bit. I interpreted the comment to describe not what generally is possible, but rather what macros are implemented. While changing this also add that elements after an existing element can be removed (SIMPLQ_REMOVE_AFTER). I also noticed

Re: [PATCH] gostr341001: support unwrapped private keys support

Hello, вт, 31 мар. 2020 г. в 06:20, Kinichiro Inoguchi : > > Hi, > > Where can we see the specifcation for these 3 different format, wrapped in > OCTET STRING, INTEGER and unwrapped but masked ? > I tried to find but couldn't. There is no English specification for GOST PKCS8 files yet,

Re: MSI-X for ix(4) again

On 26/03/20(Thu) 12:13, Martin Pieuchot wrote: > Previous diff had a bug in the interrupt handler refactoring that showed > up on i386. The version below has been tested on i386 and doesn't seem > to cause any regression. > > Here's the original explanation, diff below has msix toggle to "off":