Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue28のパッチイメージ #33

Closed
wants to merge 1 commit into from
Closed

Conversation

sile
Copy link
Member

@sile sile commented Apr 30, 2019

No description provided.

@@ -39,6 +39,7 @@ pub struct DataPortionAllocator {
size_to_free: BTreeSet<SizeBasedFreePortion>,
end_to_free: BTreeSet<EndBasedFreePortion>,
metrics: DataAllocatorMetrics,
pendings: Vec<DataPortion>,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

この配列の最大サイズはJournalRegionOptions.sync_intervalになる(はず)。

@@ -224,7 +230,11 @@ where
/// 不整合ないしI/O周りで致命的な問題が発生している可能性があるので、
/// 以後はこのインスタンスの使用を中止するのが望ましい.
pub fn delete(&mut self, lump_id: &LumpId) -> Result<bool> {
track!(self.delete_if_exists(lump_id, true))
let deleted = track!(self.delete_if_exists(lump_id, true))?;
if !self.journal_region.is_dirty() {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NVMバッファの未フラッシュの書き込みデータがないなら、allocatorの状態を同期する。
(もっと良い条件判定方法がありそうだけど、とりあえず手抜きで簡単な方法を採用)

@sile
Copy link
Member Author

sile commented May 28, 2019

#34 に引き継がれているのでこちらはクローズします。

@sile sile closed this May 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant