Opened 11 years ago
Closed 11 years ago
#40759 closed enhancement (invalid)
Support of AES-NI in encfs
| Reported by: | macports@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | Cc: | Markus.Ueberall@… | |
| Port: | encfs |
Description
I am using MacPorts 2.2.0 and built encfs @1.7.4_1 (fuse) on my Macbook Pro (Core i7, 8GB RAM). When I backup files to an internal SMB-Server with an encfs-overlay, the performance is way too slow, although my network link is 1GB. The following is an example of rsync trying to copy my video camera files with an average of 1.5MB/s:
/DCIM/100CANON/IMG_1268.JPG
3887630 100% 1.41MB/s 0:00:02 (xfer#221, to-check=1153/14004)
/DCIM/100CANON/MVI_1207.MOV
75278588 100% 1.49MB/s 0:00:48 (xfer#222, to-check=1152/14004)
/DCIM/100CANON/MVI_1208.MOV
113705816 100% 1.48MB/s 0:01:13 (xfer#223, to-check=1151/14004)
/DCIM/100CANON/MVI_1209.MOV
120240904 100% 1.54MB/s 0:01:14 (xfer#224, to-check=1150/14004)
/DCIM/100CANON/MVI_1210.MOV
Is it possible to include Intels AES-NI feature into encfs and thus improve the performance?
Change History (1)
comment:1 Changed 11 years ago by raimue (Rainer Müller)
| Cc: | Markus.Ueberall@… added |
|---|---|
| Keywords: | aesni encfs removed |
| Resolution: | → invalid |
| Status: | new → closed |
Please remember to set the port field and add the maintainer.
If upstream supports a feature, we can enable it. Development of new features has to be done upstream. See also this ticket upstream, http://code.google.com/p/encfs/issues/detail?id=70. If the openssl port does not support or use AES-NI on your machine although it should, please open a new ticket against openssl.