Re: Getting started with ktls

2021-03-10 Thread Alan Somers
On Wed, Mar 10, 2021 at 8:15 PM Benjamin Kaduk wrote: > On Wed, Mar 10, 2021 at 06:17:42PM -0700, Alan Somers wrote: > > On Wed, Mar 10, 2021 at 5:31 PM Benjamin Kaduk wrote: > > > > > On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > > > > I'm trying to make ktls work with "zfs

Re: Getting started with ktls

2021-03-10 Thread Benjamin Kaduk
On Wed, Mar 10, 2021 at 06:17:42PM -0700, Alan Somers wrote: > On Wed, Mar 10, 2021 at 5:31 PM Benjamin Kaduk wrote: > > > On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > > > I'm trying to make ktls work with "zfs send/recv" to substantially reduce > > > the CPU utilization of

Re: FYI: main (bad9fa56620e based): some unexpected SIGSEGV's using poudriere-devel to build armv7 ports on aarch64 (cortex-a72) system

2021-03-10 Thread Mark Millard via freebsd-current
On 2021-Mar-10, at 10:09, Olivier Houchard wrote: > On Tue, Mar 09, 2021 at 03:39:42PM -0800, Mark Millard via freebsd-arm wrote: >> After using poudriere to build ports for native cortex-a72 >> on the MACCHIATObin Double Shot (and similarly for >> cortex-a57 on the OverDrive 1000) I

Re: Getting started with ktls

2021-03-10 Thread Alan Somers
On Wed, Mar 10, 2021 at 5:31 PM Benjamin Kaduk wrote: > On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > > I'm trying to make ktls work with "zfs send/recv" to substantially reduce > > the CPU utilization of applications like zrepl. But I have a few > questions: > > > > *

Re: Getting started with ktls

2021-03-10 Thread Benjamin Kaduk
On Wed, Mar 10, 2021 at 05:18:24PM -0700, Alan Somers wrote: > I'm trying to make ktls work with "zfs send/recv" to substantially reduce > the CPU utilization of applications like zrepl. But I have a few questions: > > * ktls(4)'s "Transmit" section says "Once TLS transmit is enabled by a >

Getting started with ktls

2021-03-10 Thread Alan Somers
I'm trying to make ktls work with "zfs send/recv" to substantially reduce the CPU utilization of applications like zrepl. But I have a few questions: * ktls(4)'s "Transmit" section says "Once TLS transmit is enabled by a successful set of the TCP_TXTLS_ENABLE socket option", but the "Supported

Re: FYI: main (bad9fa56620e based): some unexpected SIGSEGV's using poudriere-devel to build armv7 ports on aarch64 (cortex-a72) system

2021-03-10 Thread Olivier Houchard
Hi Mark, On Tue, Mar 09, 2021 at 03:39:42PM -0800, Mark Millard via freebsd-arm wrote: > After using poudriere to build ports for native cortex-a72 > on the MACCHIATObin Double Shot (and similarly for > cortex-a57 on the OverDrive 1000) I attempted to do my > usual bulk build targeting cortex-a7

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

2021-03-10 Thread David Wolfskill
On Wed, Mar 10, 2021 at 08:25:00AM -0700, Warner Losh wrote: > ... > > Also (as yesterday), neither laptop exhibited a problem after the > > corresponding update. > > > > Yes it "works" without invariants. I'm working on a better fix that isn't > such a huge game of whack-a-mole that defers the

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

2021-03-10 Thread Warner Losh
On Wed, Mar 10, 2021 at 5:37 AM David Wolfskill wrote: > On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote: > > On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill > wrote: > > ... > > > uma_zalloc_debug: zone "malloc-1024"umass0 on uhub2 > > > with the following non-sleepable locks held:

Re: panic: malloc(M_WAITOK) with sleeping prohibited

2021-03-10 Thread Peter Holm
On Wed, Mar 10, 2021 at 01:33:34PM +0100, Hans Petter Selasky wrote: > On 3/10/21 12:41 PM, Peter Holm wrote: > > On Wed, Mar 10, 2021 at 10:52:53AM +0100, Hans Petter Selasky wrote: > >> On 3/10/21 10:15 AM, Peter Holm wrote: > >>> I just got this panic: > >>> > >>> igb0: port 0xd020-0xd03f >

Re: "panic: malloc(M_WAITOK) with sleeping prohibited" at main-n245363-b3dac3913dc9

2021-03-10 Thread David Wolfskill
On Tue, Mar 09, 2021 at 04:04:56PM -0700, Warner Losh wrote: > On Tue, Mar 9, 2021 at 2:46 PM David Wolfskill wrote: > ... > > uma_zalloc_debug: zone "malloc-1024"umass0 on uhub2 > > with the following non-sleepable locks held: > > umass0: on usbus0 > > exclusive sleep mutex CAM device

Re: panic: malloc(M_WAITOK) with sleeping prohibited

2021-03-10 Thread Hans Petter Selasky
On 3/10/21 12:41 PM, Peter Holm wrote: On Wed, Mar 10, 2021 at 10:52:53AM +0100, Hans Petter Selasky wrote: On 3/10/21 10:15 AM, Peter Holm wrote: I just got this panic: igb0: port 0xd020-0xd03f mem 0xfb32-0xfb33,0xfb344000-0xfb347fff irq 16 at device 0.0 on pci8 igb0: Using 1024 TX

Re: panic: malloc(M_WAITOK) with sleeping prohibited

2021-03-10 Thread Peter Holm
On Wed, Mar 10, 2021 at 10:52:53AM +0100, Hans Petter Selasky wrote: > On 3/10/21 10:15 AM, Peter Holm wrote: > > I just got this panic: > > > > igb0: port 0xd020-0xd03f mem > > 0xfb32-0xfb33,0xfb344000-0xfb347fff irq 16 at device 0.0 on pci8 > > igb0: Using 1024 TX descriptors and 1024

Re: panic: malloc(M_WAITOK) with sleeping prohibited

2021-03-10 Thread Hans Petter Selasky
On 3/10/21 10:15 AM, Peter Holm wrote: I just got this panic: igb0: port 0xd020-0xd03f mem 0xfb32-0xfb33,0xfb344000-0xfb347fff irq 16 at device 0.0 on pci8 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: queue equality override not set, capping rx_queues at 6 and

panic: malloc(M_WAITOK) with sleeping prohibited

2021-03-10 Thread Peter Holm
I just got this panic: igb0: port 0xd020-0xd03f mem 0xfb32-0xfb33,0xfb344000-0xfb347fff irq 16 at device 0.0 on pci8 igb0: Using 1024 TX descriptors and 1024 RX descriptors igb0: queue equality override not set, capping rx_queues at 6 and tx_queues at 6 igb0: Using 6 RX queues 6 TX