-
Notifications
You must be signed in to change notification settings - Fork 225
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
Sync ReadLimiter #201
Sync ReadLimiter #201
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,6 +29,7 @@ mod primitive; | |
pub mod layout; | ||
mod mask; | ||
pub mod units; | ||
mod read_limiter; | ||
mod zero; | ||
|
||
#[cfg(test)] | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,92 @@ | ||
// Copyright (c) 2013-2015 Sandstorm Development Group, Inc. and contributors | ||
// Licensed under the MIT License: | ||
// | ||
// Permission is hereby granted, free of charge, to any person obtaining a copy | ||
// of this software and associated documentation files (the "Software"), to deal | ||
// in the Software without restriction, including without limitation the rights | ||
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
// copies of the Software, and to permit persons to whom the Software is | ||
// furnished to do so, subject to the following conditions: | ||
// | ||
// The above copyright notice and this permission notice shall be included in | ||
// all copies or substantial portions of the Software. | ||
// | ||
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN | ||
// THE SOFTWARE. | ||
|
||
#[cfg(feature = "sync_reader")] | ||
pub use sync::ReadLimiter; | ||
|
||
#[cfg(feature = "sync_reader")] | ||
mod sync { | ||
use crate::{Error, Result}; | ||
use core::sync::atomic::{AtomicUsize, Ordering}; | ||
|
||
pub struct ReadLimiter { | ||
pub limit: usize, | ||
pub read: AtomicUsize, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Making this an There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The issue with |
||
} | ||
|
||
impl ReadLimiter { | ||
pub fn new(limit: u64) -> ReadLimiter { | ||
if limit > core::usize::MAX as u64 { | ||
panic!("traversal_limit_in_words cannot be bigger than core::usize::MAX") | ||
} | ||
|
||
ReadLimiter { | ||
limit: limit as usize, | ||
read: AtomicUsize::new(0), | ||
} | ||
} | ||
|
||
#[inline] | ||
pub fn can_read(&self, amount: usize) -> Result<()> { | ||
let read = self.read.load(Ordering::Relaxed) + amount; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It looks to me like this can overflow if Why not write this is the same way as the non- There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, unless I don't see an obvious solution here, the way it's done in the non-sync version is possible because it's single threaded. In a multi-threaded version, I need to make sure that the limit underflowing is handled correctly. If I was to get then sub without checking underflow, the limit would wrap around and allows the next readers to read I think the version I pushed is better and handle this better than my previous version. I use an extra flag to indicate that the limit has been reached when the limit got to 0 or when it underflows. |
||
|
||
if read > self.limit { | ||
Err(Error::failed(format!("read limit exceeded"))) | ||
} else { | ||
self.read.fetch_add(amount, Ordering::Relaxed); | ||
Ok(()) | ||
} | ||
} | ||
} | ||
} | ||
|
||
#[cfg(not(feature = "sync_reader"))] | ||
pub use unsync::ReadLimiter; | ||
|
||
#[cfg(not(feature = "sync_reader"))] | ||
mod unsync { | ||
use core::cell::Cell; | ||
use crate::{Error, Result}; | ||
|
||
pub struct ReadLimiter { | ||
pub limit: Cell<u64>, | ||
} | ||
|
||
impl ReadLimiter { | ||
pub fn new(limit: u64) -> ReadLimiter { | ||
ReadLimiter { | ||
limit: Cell::new(limit), | ||
} | ||
} | ||
|
||
#[inline] | ||
pub fn can_read(&self, amount: usize) -> Result<()> { | ||
let amount = amount as u64; | ||
let current = self.limit.get(); | ||
if amount > current { | ||
Err(Error::failed(format!("read limit exceeded"))) | ||
} else { | ||
self.limit.set(current - amount); | ||
Ok(()) | ||
} | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to make the new feature not a default feature, so that we minimize the chance of breaking anyone's code.