[Bug 242747] geli: AMD Epyc+GELI not using Hardware AES

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242747

--- Comment #10 from Nick Evans <nevans at talkpoint.com> ---
(In reply to dewayne from comment #8)

So far results are the same with both boxes being on -CURRENT with NODEBUG
kernels so at least that's ruled out.


eli.batch=1 alone helps CPU the usage, but at the expense of throughput. At
least on the Epyc box. It goes from about 280MB/s per disk to 180MB/s.
Idle-ness went up to 60% but probably due to the drop in overall throughput. 

The eli.threads=2 count makes a big difference on the Epyc box. Per disk
throughput went up to 330MB/s and the overall idle-ness went up to 92% running
dd if=/dev/da#.eli of=/dev/null bs=1m one per disk. batch=1 even with threads=2
doesn't seem to help in this case.

I guess there's some kind of thrashing going on here when the default 32
threads per disk are created that affects the Epyc box more than the Xeon. I'll
run some tests are different thread numbers and report back. Maybe we can at
least come up with more sensible defaults.

-- 
You are receiving this mail because:
You are the assignee for the bug.