AFAIK, there are already internal beta builds available for that model based on 382, so I expect they will eventually migrate that model to it.
The only device they specifically mentioned as being excluded when discussing it was the RT-N16.
I already squeezed everything I could out of openssl on these older ARM processors (including backporting optimizations from newer openssl releases at the time). For the RT-AC86U I don't know yet, optimization is far at the bottom of my list of things to do. Here are the current results using Asus's default optimizations on the RT-AC86U:
Code:
OpenSSL 1.0.2j 26 Sep 2016
built on: reproducible build, date unspecified
options:bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) aes(partial) idea(int) blowfish(ptr)
compiler: /opt/toolchains/crosstools-arm-gcc-5.3-linux-4.1-glibc-2.22-binutils-2.25/usr/bin/arm-buildroot-linux-gnueabi-gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_HEARTBEATS -DL_ENDIAN -Os -march=armv7-a -fomit-frame-pointer -mabi=aapcs-linux -marm -ffixed-r8 -msoft-float -D__ARM_ARCH_7A__ -ffunction-sections -fdata-sections -O3 -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DAES_ASM -DBSAES_ASM -DGHASH_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 19452.99k 70705.77k 226198.86k 496435.88k 769111.38k
aes-128 cbc 67813.30k 74312.02k 77161.30k 78323.33k 78692.19k
aes-192 cbc 58153.93k 64428.71k 66564.44k 66911.77k 67012.75k
aes-256 cbc 52080.34k 56746.70k 58479.70k 58827.27k 59176.28k
sha256 43923.10k 151693.35k 383434.08k 621045.04k 762250.53k
sha512 11354.54k 45011.22k 70937.43k 99912.70k 113602.08k