mirror of
https://github.com/saymrwulf/xous-core.git
synced 2026-11-18 08:52:45 +00:00
chore: fix another typo
This commit is contained in:
parent
8f85aefa27
commit
0d65d9a7ca
1 changed files with 1 additions and 1 deletions
|
|
@ -49,7 +49,7 @@ pub(crate) struct DictCacheEntry {
|
||||||
/// read in, and is the "master" for tracking purposes. We always fill this from index 0 and go up; if a KeySmallPool
|
/// read in, and is the "master" for tracking purposes. We always fill this from index 0 and go up; if a KeySmallPool
|
||||||
/// goes completely empty, the entry should still exist but indicate that it's got space. Thus if a key was found allocated
|
/// goes completely empty, the entry should still exist but indicate that it's got space. Thus if a key was found allocated
|
||||||
/// to the Nth index position, but the previous N-1 positions are empty, the only way we could have gotten there was if we
|
/// to the Nth index position, but the previous N-1 positions are empty, the only way we could have gotten there was if we
|
||||||
/// had allocated lots of small data, filled upo the pool to the Nth position, and then deleted all of that prior data.
|
/// had allocated lots of small data, filled up the pool to the Nth position, and then deleted all of that prior data.
|
||||||
/// This situation could create pathologies in the memory usage overhead of the small_pool, which until we have a "defrag"
|
/// This situation could create pathologies in the memory usage overhead of the small_pool, which until we have a "defrag"
|
||||||
/// operation for the small pool, we may just have to live with.
|
/// operation for the small pool, we may just have to live with.
|
||||||
pub(crate) small_pool: Vec<KeySmallPool>,
|
pub(crate) small_pool: Vec<KeySmallPool>,
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue