Re: how to use the ktls

2020-01-08 Thread John Baldwin
On 1/7/20 3:02 PM, Rick Macklem wrote: > Hi, > > Now that I've completed NFSv4.2 I'm on to the next project, which is making > NFS > work over TLS. > Of course, I know absolutely nothing about TLS, which will make this an > interesting > exercise for me. > I did find simple server code in the Op

QUER DESINCHAR SUA BARRIGA EM 72hrs.. PERCA DE 5 a 10kg.. AGORA!! (24889)

2020-01-08 Thread current
___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

head -356426 based 32-bit powerpc (2 sock PowerMac G4): kyua sys/vm/mlock_test:mlock__copy_on_write_vnode seems stuck

2020-01-08 Thread Mark Millard
I've attempted a head -356426 based kyua run on an old 2-socket PowerMac G4. The buildworld and buildkernel were non-debug. The context has personal patches, mostly for dealing with PowerMac issues. It has had over 180 CPU minutes running for: sys/vm/mlock_test:mlock__copy_on_write_vnode -> N

Re: head -356426 based 32-bit powerpc (2 sock PowerMac G4): kyua sys/vm/mlock_test:mlock__copy_on_write_vnode seems stuck

2020-01-08 Thread Mark Millard
[I got kernel backtrace information, included.] On 2020-Jan-8, at 15:12, Mark Millard wrote: > I've attempted a head -356426 based kyua run on an > old 2-socket PowerMac G4. The buildworld and > buildkernel were non-debug. The context has personal > patches, mostly for dealing with PowerMac issu

Re: head -356426 based 32-bit powerpc (2 sock PowerMac G4): kyua sys/vm/mlock_test:mlock__copy_on_write_vnode seems stuck

2020-01-08 Thread Mark Millard
[Even the artifacts debug-style kernel gets the problem. More evidence of context extracted and supplied.] On 2020-Jan-8, at 18:09, Mark Millard wrote: > [I got kernel backtrace information, included.] > > On 2020-Jan-8, at 15:12, Mark Millard wrote: > >> I've attempted a head -356426 based k