GPU Encrypt: AES Encryption on Mobile Devices

James Gleeson, Sreekumar Rajan, Vandana Saini
Department of Computer Science, University of Toronto, Toronto, ON
University of Toronto, 2014

   title={GPU Encrypt: AES Encryption on Mobile Devices},

   author={Gleeson, James and Rajan, Sreekumar and Saini, Vandana},



Download Download (PDF)   View View   Source Source   



In this report, we have taken the first steps in investigating the feasibility of using the GPU as a cryptographic accelerator for the AES algorithm on mobile devices. In particular, our focus was on exploring the use of OpenCL as a framework for implementing the algorithm. Using modifications of an existing implementation [11], we first showed that OpenCL schedules work groups to execute exclusively on the compute units of the GPU, and that optimal throughput must be achieved through more than just a simple data parallel implementation. Next, we investigated how performance varied with the implementation as the number of active work items in a single compute unit was varied, discovering a surprising level off in encryption throughput when using only 1/4 of the available work items. Next we investigated two potential reasons for lower than expected performance: strided access to input data within work groups, and redundant random accesses to the T-box lookup table that could be avoided using local memory. We discovered the T-box lookup table optimization provided the best increase in throughput, whereas the coalesced access implementation only added to the runtime. Finally, we determined that using optimal parameters for the number of work groups and work group size, we were able to achieve a 1.79 fold speedup in maximum throughput over a single CPU using the OpenSSL implementation.
VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

* * *

* * *

TwitterAPIExchange Object
    [oauth_access_token:TwitterAPIExchange:private] => 301967669-yDz6MrfyJFFsH1DVvrw5Xb9phx2d0DSOFuLehBGh
    [oauth_access_token_secret:TwitterAPIExchange:private] => o29ji3VLVmB6jASMqY8G7QZDCrdFmoTvCDNNUlb7s
    [consumer_key:TwitterAPIExchange:private] => TdQb63pho0ak9VevwMWpEgXAE
    [consumer_secret:TwitterAPIExchange:private] => Uq4rWz7nUnH1y6ab6uQ9xMk0KLcDrmckneEMdlq6G5E0jlQCFx
    [postfields:TwitterAPIExchange:private] => 
    [getfield:TwitterAPIExchange:private] => ?cursor=-1&screen_name=hgpu&skip_status=true&include_user_entities=false
    [oauth:protected] => Array
            [oauth_consumer_key] => TdQb63pho0ak9VevwMWpEgXAE
            [oauth_nonce] => 1477106941
            [oauth_signature_method] => HMAC-SHA1
            [oauth_token] => 301967669-yDz6MrfyJFFsH1DVvrw5Xb9phx2d0DSOFuLehBGh
            [oauth_timestamp] => 1477106941
            [oauth_version] => 1.0
            [cursor] => -1
            [screen_name] => hgpu
            [skip_status] => true
            [include_user_entities] => false
            [oauth_signature] => Yoz48hXsM0BpIt2F2E51EWm3Gb0=

    [url] => https://api.twitter.com/1.1/users/show.json
Follow us on Facebook
Follow us on Twitter

HGPU group

2033 peoples are following HGPU @twitter

HGPU group © 2010-2016 hgpu.org

All rights belong to the respective authors

Contact us: