Buffer Free Bytes after Reservation
Audit a proposed byte-buffer reservation retaining negative free-space evidence; does not allocate memory or silently clamp over-reservation.
Description
Audit a proposed byte-buffer reservation retaining negative free-space evidence; does not allocate memory or silently clamp over-reservation.
Reservation arithmetic can produce negative free space. Preserving that sign exposes an over-reservation rather than silently clipping it.
When to use this tool
Audit a proposed byte-buffer reservation retaining negative free-space evidence; does not allocate memory or silently clamp over-reservation.
- Prepare the supplied capacity, used, reservation fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter capacity, used, reservation. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.freeBytes, result.overReserved. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate integer capacity, used within capacity and nonnegative reservation. freeBytes is capacity minus used minus reservation; overReserved is true when used plus reservation exceeds capacity.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| capacity | capacity. | Integer from 0 to 1e9 inclusive |
| used | used. | Integer from 0 to capacity inclusive |
| reservation | reservation. | Integer from 0 to 1e9 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.freeBytes | The free bytes value under the stated formula or text convention. |
| result.overReserved | Flag for over reserved under the exact condition described above. |
{
"input": {
"capacity": 100,
"used": 70,
"reservation": 40
},
"output": {
"result": {
"freeBytes": -10,
"overReserved": true
}
}
}Limitations and assumptions
- No memory is allocated or reserved. The result does not account for fragmentation or platform overhead.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Check the arithmetic against the actual scheduling or storage policy. Add variable costs, arrivals, concurrent state and overhead in a model that explicitly represents them when they affect the decision.
References
Similar or alternative tools
- Buffer Equal Record Slot Count
Budget fixed-byte records after an explicit buffer header reservation, retaining unused tail bytes.
- Buffer Growing Record Budget
Admit complete records whose byte sizes grow arithmetically from an explicit initial size; bounded to 128 records with signed residual budget evidence.