Re: [PATCH v5] mmc: fix async request mechanism for sequential read scenarios

2013-01-15 Thread Konstantin Dorfman
On 01/14/2013 09:31 PM, Chris Ball wrote: Hi Konstantin, On Fri, Dec 28 2012, Seungwon Jeon wrote: I checked the changes. Thanks for your work. Reviewed-by: Seungwon Jeon On Wednesday, December 26, 2012, Konstantin Dorfman wrote: When current request is running on the bus and if next reques

Re: [PATCH v5] mmc: fix async request mechanism for sequential read scenarios

2013-01-14 Thread Chris Ball
Hi Konstantin, On Fri, Dec 28 2012, Seungwon Jeon wrote: > I checked the changes. Thanks for your work. > > Reviewed-by: Seungwon Jeon > > On Wednesday, December 26, 2012, Konstantin Dorfman wrote: >> When current request is running on the bus and if next request fetched >> by mmcqd is NULL, mmc

RE: [PATCH v5] mmc: fix async request mechanism for sequential read scenarios

2012-12-28 Thread Seungwon Jeon
I checked the changes. Thanks for your work. Reviewed-by: Seungwon Jeon On Wednesday, December 26, 2012, Konstantin Dorfman wrote: > When current request is running on the bus and if next request fetched > by mmcqd is NULL, mmc context (mmcqd thread) gets blocked until the > current request comp

[PATCH v5] mmc: fix async request mechanism for sequential read scenarios

2012-12-26 Thread Konstantin Dorfman
When current request is running on the bus and if next request fetched by mmcqd is NULL, mmc context (mmcqd thread) gets blocked until the current request completes. This means that if new request comes in while the mmcqd thread is blocked, this new request can not be prepared in parallel to curren