On Thu, Aug 03, 2023 at 03:03:06PM +0930, Brett Lymn wrote:
> > If anyone cares about veriexec(4) and would like to volunteer to take
> > this on, we can discuss what needs to be done and how to proceed.
>
> I will take this on since I was originally responsible for the mess. It
> does play
> On 4. Aug 2023, at 21:48, Jaromír Doleček wrote:
> In a broader view, I have doubts if there is any practical reason to
> even have support for bigger than 64kb block size support at all.
Having tapes with record size > 64k would be a real benefit though.
--
J. Hannken-Illjes -
Le ven. 4 août 2023 à 17:27, Jason Thorpe a écrit :
> If someone does pick this up, I think it would be a good idea to start from
> scratch, because MAXPHYS, as it stands, is used for multiple things.
> Thankfully, I think it would be relatively straightforward to do the work
> that I am
Hi,
iwm driver has one watchdog timer for the aggregate Tx queue. And it resets the
interface when the watchdog fires resulting in loss of connectivity. The
workaround for this issue is executing
ifconfig iwm0 down
ifconfig iwm0 up
Here is the dump of logs when this reset happens:
[
> On Aug 3, 2023, at 2:19 PM, Brian Buhrow wrote:
>
> hello. I know that this has ben a very long term project, but I'm wondering
> about the
> status of this effort? I note that FreeBSD-13 has a Maxphys value of 1048576
> bytes.
> Have we found other ways to get more throughput from ATA
On Thu, Aug 03, 2023 at 11:04:18PM -0700, Brian Buhrow wrote:
> speed of the transfers on either system. Interestingly enough, however, the
> FreeBSD
> performance is markedly worse on this test.
162MB/s or 179MB/s is just the speed of the disk, so I would guess the
disks are different.
Hasn't there been a tls-maxphys branch?
hello. Michael's e-mail explains the behavior I'm seeing with trying
different block
sizes with NetBSD and FreeBSD.
The scripts below show transfers of the same number of bytes using 1m and 64k
block sizes for
NetBSD-9.99.77/amd64 and FreeBSD-13.1/amd64. NetBSD is using SATA3 disks
