On Aug 16, 2017 11:41 PM, "Markus Armbruster" wrote:
Eric Blake writes:
> On 08/16/2017 11:13 AM, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>
>>>
>>> Conclusion: no consensus, yet.
>>
>> All right, let's start over and try to resolve the impasse and/or
>> misunderstanding.
>>
>>
Eric Blake writes:
> On 08/16/2017 11:13 AM, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>
>>>
>>> Conclusion: no consensus, yet.
>>
>> All right, let's start over and try to resolve the impasse and/or
>> misunderstanding.
>>
>> Type BlockIOThrottle lives in qapi/block-core.json,
On 08/16/2017 11:13 AM, Markus Armbruster wrote:
> Markus Armbruster writes:
>
>>
>> Conclusion: no consensus, yet.
>
> All right, let's start over and try to resolve the impasse and/or
> misunderstanding.
>
> Type BlockIOThrottle lives in qapi/block-core.json, and is used by QMP
> command blo
Markus Armbruster writes:
> Eric Blake writes:
>
>> On 08/10/2017 09:06 AM, Pradeep Jagadeesh wrote:
>>
> It's not "moving it back", it's keeping it where it is. But I see no big
> problem with moving it to a common file either.
I'd rather not put every struct shared across sub
Eric Blake writes:
> On 08/10/2017 09:06 AM, Pradeep Jagadeesh wrote:
>
It's not "moving it back", it's keeping it where it is. But I see no big
problem with moving it to a common file either.
>>>
>>> I'd rather not put every struct shared across subsystem boundaries in
>>> its own file
On 08/10/2017 09:06 AM, Pradeep Jagadeesh wrote:
>>> It's not "moving it back", it's keeping it where it is. But I see no big
>>> problem with moving it to a common file either.
>>
>> I'd rather not put every struct shared across subsystem boundaries in
>> its own file.
>>
>> We can keep it right
On 8/8/2017 5:18 PM, Markus Armbruster wrote:
Alberto Garcia writes:
On Tue 08 Aug 2017 02:30:43 PM CEST, Pradeep Jagadeesh wrote:
On 8/8/2017 1:30 PM, Alberto Garcia wrote:
On Mon 07 Aug 2017 04:48:38 PM CEST, Markus Armbruster wrote:
Awkward question for a v7, but here goes anyway: why is
Alberto Garcia writes:
> On Tue 08 Aug 2017 02:30:43 PM CEST, Pradeep Jagadeesh wrote:
>> On 8/8/2017 1:30 PM, Alberto Garcia wrote:
>>> On Mon 07 Aug 2017 04:48:38 PM CEST, Markus Armbruster wrote:
>> Awkward question for a v7, but here goes anyway: why is IOThrottle
>> worth its very ow
On Tue 08 Aug 2017 02:30:43 PM CEST, Pradeep Jagadeesh wrote:
> On 8/8/2017 1:30 PM, Alberto Garcia wrote:
>> On Mon 07 Aug 2017 04:48:38 PM CEST, Markus Armbruster wrote:
> Awkward question for a v7, but here goes anyway: why is IOThrottle
> worth its very own .json file?
I feel this
On 8/8/2017 1:30 PM, Alberto Garcia wrote:
On Mon 07 Aug 2017 04:48:38 PM CEST, Markus Armbruster wrote:
Awkward question for a v7, but here goes anyway: why is IOThrottle
worth its very own .json file?
I feel this is a common throttle structure that is used by block
devices as well as fsdev, s
On Mon 07 Aug 2017 04:48:38 PM CEST, Markus Armbruster wrote:
>>> Awkward question for a v7, but here goes anyway: why is IOThrottle
>>> worth its very own .json file?
>> I feel this is a common throttle structure that is used by block
>> devices as well as fsdev, so moved to a separate file.
> I'm
Pradeep Jagadeesh writes:
> On 7/6/2017 7:55 PM, Markus Armbruster wrote:
>> Pradeep Jagadeesh writes:
>>
>>> This patch enables qmp interfaces for the fsdev
>>> devices. This provides two interfaces one
>>> for querying info of all the fsdev devices. The second one
>>> to set the IO limits for
On 7/6/2017 7:55 PM, Markus Armbruster wrote:
Pradeep Jagadeesh writes:
This patch enables qmp interfaces for the fsdev
devices. This provides two interfaces one
for querying info of all the fsdev devices. The second one
to set the IO limits for the required fsdev device.
Signed-off-by: Prade
Pradeep Jagadeesh writes:
> This patch enables qmp interfaces for the fsdev
> devices. This provides two interfaces one
> for querying info of all the fsdev devices. The second one
> to set the IO limits for the required fsdev device.
>
> Signed-off-by: Pradeep Jagadeesh
> Reviewed-by: Greg Kur
This patch enables qmp interfaces for the fsdev
devices. This provides two interfaces one
for querying info of all the fsdev devices. The second one
to set the IO limits for the required fsdev device.
Signed-off-by: Pradeep Jagadeesh
Reviewed-by: Greg Kurz
Reviewed-by: Eric Blake
Reviewed-by:
15 matches
Mail list logo
