diff options
author | lloyd <[email protected]> | 2012-06-20 16:45:46 +0000 |
---|---|---|
committer | lloyd <[email protected]> | 2012-06-20 16:45:46 +0000 |
commit | b5753ba9469450adde1136c5d50e82b4cad7b658 (patch) | |
tree | 235faa83a76a128b2690c75616a328c5ec269565 /doc/building.txt | |
parent | 38acefedb83e291d13431a85120c942a389e0b99 (diff) |
Split log.txt into individual release notes. Integrate most of the
relevant contents from the pyblosxom news site into said relnotes.
DRY suggests having only one form of release notes, and having it in
the public source repo.
Also some updates for the allocator changes.
Diffstat (limited to 'doc/building.txt')
-rw-r--r-- | doc/building.txt | 13 |
1 files changed, 2 insertions, 11 deletions
diff --git a/doc/building.txt b/doc/building.txt index e16531de4..cc6f0af5d 100644 --- a/doc/building.txt +++ b/doc/building.txt @@ -331,18 +331,9 @@ for calculations with the MPI implementation in Botan. You can choose on the processor. Unless you are building for a 8 or 16-bit CPU, this isn't worth messing with. -``BOTAN_VECTOR_OVER_ALLOCATE``: The memory container ``SecureVector`` -will over-allocate requests by this amount (in elements). In several -areas of the library, we grow a vector fairly often. By -over-allocating by a small amount, we don't have to do allocations as -often (which is good, because the allocators can be quite slow). If -you *really* want to reduce memory usage, set it to 0. Otherwise, the -default should be perfectly fine. - ``BOTAN_DEFAULT_BUFFER_SIZE``: This constant is used as the size of -buffers throughout Botan. A good rule of thumb would be to use the -page size of your machine. The default should be fine for most -purposes. +buffers throughout Botan. The default should be fine for most +purposes, reduce if you are very concerned about runtime memory usage. Building Applications ---------------------------------------- |