Hi Jens
>> Add support for reinserting a dispatched request back to the
>> scheduler's internal data structures.
>> This capability is used by the device driver when it chooses to
>> interrupt the current request transmission and execute another (more
>> urgent) pending request. For example: inter
From: Tatyana Brokhman
This patch add support for handling urgent requests.
ROW queue can be marked as "urgent" so if it was un-served and a
request was added to it - it will trigger issuing urgent request
to the mmc driver.
Signed-off-by: Tatyana Brokhman
diff --git a/block/row-iosched.c b/bl
From: Tatyana Brokhman
Add support for reinserting already dispatched request back to the
schedulers internal data structures.
The request will be reinserted back to the queue (head) it was
dispatched from as if it was never dispatched.
Signed-off-by: Tatyana Brokhman
diff --git a/block/row-io
This patch set add support for handling urgent requests by the
ROW algorith. It depends on 2 previosly uploaded patch sets:
1. ROW scheduling Algorithm
2. Adding support for urgent requests handling
Tatyana Brokhman (2):
row: Adding support for reinsert already dispatched req
row: Add support
From: Tatyana Brokhman
This patch add support in block & elevator layers for handling
urgent requests.
Urgent request notification passed to underlying driver (eMMC for
example) and causes interruption of low priority current request in
order to execute the urgent one.
Signed-off-by: Tatyana Bro
From: Tatyana Brokhman
Add support for reinserting a dispatched request back to the
schedulers internal data structures.
Add API for verifying whether the current scheduler
supports reinserting requests mechanism
Signed-off-by: Tatyana Brokhman
diff --git a/block/blk-core.c b/block/blk-core.c
This patch set adds support in block & elevator layers for handling
urgent requests.
Urgent request notification passed to underlying driver (eMMC for
example) and causes interruption of low priority current request in
order to execute the urgent one.
The interrupted request is inserted back to the
From: Tatyana Brokhman
This patch adds the implementation of a new scheduling algorithm - ROW.
The policy of this algorithm is to prioritize READ requests over WRITE
as much as possible without starving the WRITE requests.
Signed-off-by: Tatyana Brokhman
diff --git a/Documentation/block/row-io
From: Tatyana Brokhman
ROW is a new scheduling algorithm. Similar to the existing scheduling
algorithms it should be compiled to the kernel statically giving the user
the ability to switch to it without kernel recompilation.
Signed-off-by: Tatyana Brokhman
diff --git a/block/Kconfig.iosched b/
From: Tatyana Brokhman
The ROW scheduling algorithm will be used in mobile devices as default
block layer IO scheduling algorithm. ROW stands for "READ Over WRITE"
which is the main requests dispatch policy of this algorithm.
The ROW IO scheduler was developed with the mobile devices needs in
mi
10 matches
Mail list logo
