tmp/tmplnzdxd7b/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,29 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
#### `pool_options` data members <a id="mem.res.pool.options">[[mem.res.pool.options]]</a>
|
| 2 |
+
|
| 3 |
+
The members of `pool_options` comprise a set of constructor options for
|
| 4 |
+
pool resources. The effect of each option on the pool resource behavior
|
| 5 |
+
is described below:
|
| 6 |
+
|
| 7 |
+
``` cpp
|
| 8 |
+
size_t max_blocks_per_chunk;
|
| 9 |
+
```
|
| 10 |
+
|
| 11 |
+
The maximum number of blocks that will be allocated at once from the
|
| 12 |
+
upstream memory resource ([[mem.res.monotonic.buffer]]) to replenish a
|
| 13 |
+
pool. If the value of `max_blocks_per_chunk` is zero or is greater than
|
| 14 |
+
an *implementation-defined* limit, that limit is used instead. The
|
| 15 |
+
implementation may choose to use a smaller value than is specified in
|
| 16 |
+
this field and may use different values for different pools.
|
| 17 |
+
|
| 18 |
+
``` cpp
|
| 19 |
+
size_t largest_required_pool_block;
|
| 20 |
+
```
|
| 21 |
+
|
| 22 |
+
The largest allocation size that is required to be fulfilled using the
|
| 23 |
+
pooling mechanism. Attempts to allocate a single block larger than this
|
| 24 |
+
threshold will be allocated directly from the upstream memory resource.
|
| 25 |
+
If `largest_required_pool_block` is zero or is greater than an
|
| 26 |
+
*implementation-defined* limit, that limit is used instead. The
|
| 27 |
+
implementation may choose a pass-through threshold larger than specified
|
| 28 |
+
in this field.
|
| 29 |
+
|