On Mon, Dec 18, 2017 at 1:01 PM, Vivek Goyal wrote:
> On Mon, Dec 18, 2017 at 12:39:50PM -0800, Khazhismel Kumykov wrote:
>> On Mon, Dec 18, 2017 at 10:29 AM, Vivek Goyal wrote:
>> > On Mon, Dec 18, 2017 at 10:16:02AM -0800, Khazhismel Kumykov wrote:
>> >> On Mon, Nov 20, 2017 at 8:36 PM, Khazhis
On Mon, Dec 18, 2017 at 12:39:50PM -0800, Khazhismel Kumykov wrote:
> On Mon, Dec 18, 2017 at 10:29 AM, Vivek Goyal wrote:
> > On Mon, Dec 18, 2017 at 10:16:02AM -0800, Khazhismel Kumykov wrote:
> >> On Mon, Nov 20, 2017 at 8:36 PM, Khazhismel Kumykov
> >> wrote:
> >> > On Fri, Nov 17, 2017 at 1
On Mon, Dec 18, 2017 at 10:29 AM, Vivek Goyal wrote:
> On Mon, Dec 18, 2017 at 10:16:02AM -0800, Khazhismel Kumykov wrote:
>> On Mon, Nov 20, 2017 at 8:36 PM, Khazhismel Kumykov
>> wrote:
>> > On Fri, Nov 17, 2017 at 11:26 AM, Shaohua Li wrote:
>> >> On Thu, Nov 16, 2017 at 08:25:58PM -0800, Kh
On Mon, Dec 18, 2017 at 10:16:02AM -0800, Khazhismel Kumykov wrote:
> On Mon, Nov 20, 2017 at 8:36 PM, Khazhismel Kumykov wrote:
> > On Fri, Nov 17, 2017 at 11:26 AM, Shaohua Li wrote:
> >> On Thu, Nov 16, 2017 at 08:25:58PM -0800, Khazhismel Kumykov wrote:
> >>> On Thu, Nov 16, 2017 at 8:50 AM,
On Mon, Nov 20, 2017 at 8:36 PM, Khazhismel Kumykov wrote:
> On Fri, Nov 17, 2017 at 11:26 AM, Shaohua Li wrote:
>> On Thu, Nov 16, 2017 at 08:25:58PM -0800, Khazhismel Kumykov wrote:
>>> On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
>>> > On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhisme
On Thu, Nov 16, 2017 at 08:50:33AM -0800, Shaohua Li wrote:
[..]
> Can you describe why we need this? It would be great if you can describe the
> usage model and an example. Does this work for io.low/io.max or both?
Hi Shaohua,
Is there any documentation for "io.low" somewhere now. Should we upd
On Mon, Nov 20, 2017 at 8:36 PM, Khazhismel Kumykov wrote:
> On Fri, Nov 17, 2017 at 11:26 AM, Shaohua Li wrote:
>> On Thu, Nov 16, 2017 at 08:25:58PM -0800, Khazhismel Kumykov wrote:
>>> On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
>>> > On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhisme
On Fri, Nov 17, 2017 at 11:26 AM, Shaohua Li wrote:
> On Thu, Nov 16, 2017 at 08:25:58PM -0800, Khazhismel Kumykov wrote:
>> On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
>> > On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhismel Kumykov wrote:
>> >> Allows configuration additional bytes or i
On Thu, Nov 16, 2017 at 08:25:58PM -0800, Khazhismel Kumykov wrote:
> On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
> > On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhismel Kumykov wrote:
> >> Allows configuration additional bytes or ios before a throttle is
> >> triggered.
> >>
> >> This all
On Thu, Nov 16, 2017 at 8:50 AM, Shaohua Li wrote:
> On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhismel Kumykov wrote:
>> Allows configuration additional bytes or ios before a throttle is
>> triggered.
>>
>> This allows implementation of a bucket style rate-limit/throttle on a
>> block device. P
On Tue, Nov 14, 2017 at 03:10:22PM -0800, Khazhismel Kumykov wrote:
> Allows configuration additional bytes or ios before a throttle is
> triggered.
>
> This allows implementation of a bucket style rate-limit/throttle on a
> block device. Previously, bursting to a device was limited to allowance
>
(Botched the to line, sorry)
smime.p7s
Description: S/MIME Cryptographic Signature
Allows configuration additional bytes or ios before a throttle is
triggered.
This allows implementation of a bucket style rate-limit/throttle on a
block device. Previously, bursting to a device was limited to allowance
granted in a single throtl_slice (similar to a bucket with limit N and
refill r
Allows configuration additional bytes or ios before a throttle is
triggered. Slice end is extended to cover expended allowance recovery
time.
Usage would be e.g. per device to allow users to take up to X bytes/ios
at full speed, but be limited to Y bps/iops with sustained usage.
Signed-off-by: Kh
14 matches
Mail list logo