[
https://issues.apache.org/jira/browse/HDFS-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-14417:
-------------------------------
Component/s: performance
> CryptoInputStream decrypt methods can avoid usage of intermediate buffers
> -------------------------------------------------------------------------
>
> Key: HDFS-14417
> URL: https://issues.apache.org/jira/browse/HDFS-14417
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs-client, performance
> Reporter: Sahil Takiar
> Priority: Major
>
> Filing this as a follow up to
> [this|https://github.com/apache/hadoop/pull/597#discussion_r269399800] review
> comment on HDFS-3246. In {{CryptoInputStream}} the {{decrypt}} methods rely
> on temporary buffers to help decrypt the given encrypted data. The
> {{decrypt}} methods work by copying the input data chunk by chunk into an
> "input" buffer and then passing the "input" buffer and an "output" buffer to
> a decryption method that reads from the "input" buffer and writes to the
> "output" buffer. The contents of the "output" buffer are then copied back
> into the user buffer. Then the method moves onto the next chunk of the user
> buffer.
> Instead of copying all the data between these buffers, we should be able to
> decrypt them in-place - e.g. the input and output buffer are the same. As the
> comment points out, OpenSSL supports this.
> At the very least, we should be able to remove the usage of the "output"
> buffer and just pass the user buffer directly to the decryption classes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
