On Thu, Feb 5, 2015 at 12:22 PM, Kevin Wolf wrote:
> Am 04.02.2015 um 18:51 hat Eric Blake geschrieben:
>> From: Stefan Hajnoczi
>>
>> The block.c file has grown to over 6000 lines. It is time to split this
>> file so there are fewer conflicts and the code is easier to maintain.
>>
>> Extract I/
Am 04.02.2015 um 18:51 hat Eric Blake geschrieben:
> From: Stefan Hajnoczi
>
> The block.c file has grown to over 6000 lines. It is time to split this
> file so there are fewer conflicts and the code is easier to maintain.
>
> Extract I/O request processing code:
> * Read
> * Write
> * Flush
On Wed, Feb 4, 2015 at 6:15 PM, Eric Blake wrote:
> On 02/04/2015 11:01 AM, Eric Blake wrote:
>> On 02/04/2015 10:51 AM, Eric Blake wrote:
>>> From: Stefan Hajnoczi
>>>
>>> The block.c file has grown to over 6000 lines. It is time to split this
>>> file so there are fewer conflicts and the code
On 02/04/2015 11:01 AM, Eric Blake wrote:
> On 02/04/2015 10:51 AM, Eric Blake wrote:
>> From: Stefan Hajnoczi
>>
>> The block.c file has grown to over 6000 lines. It is time to split this
>> file so there are fewer conflicts and the code is easier to maintain.
>>
>> This patch produces identica
On 02/04/2015 10:51 AM, Eric Blake wrote:
> From: Stefan Hajnoczi
>
> The block.c file has grown to over 6000 lines. It is time to split this
> file so there are fewer conflicts and the code is easier to maintain.
>
> Extract I/O request processing code:
> * Read
> * Write
> * Flush
> * Dis
From: Stefan Hajnoczi
The block.c file has grown to over 6000 lines. It is time to split this
file so there are fewer conflicts and the code is easier to maintain.
Extract I/O request processing code:
* Read
* Write
* Flush
* Discard
* ioctl
* Tracked requests and queuing
* Throttling an