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

2012-11-12 Thread Konstantin Dorfman
On 11/05/2012 08:20 AM, Per Förlin wrote: > Hi Konstantin, > > On 11/01/2012 03:40 PM, 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 completes. This means

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

2012-11-12 Thread Konstantin Dorfman
Hello Jaehoon, On 11/06/2012 10:40 AM, Jaehoon Chung wrote: > Hi Konstantin, > ... >> >> @@ -1406,6 +1401,7 @@ static int mmc_blk_issue_rq(struct mmc_queue *mq, >> struct request *req) >> ret = 0; >> goto out; >> } >> +mq->flags &= ~MMC_QUEUE_NEW_REQUEST; > I

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

2012-11-12 Thread Konstantin Dorfman
On 11/05/2012 09:15 AM, Jaehoon Chung wrote: Hello, > Hi Konstantin, > On 11/05/2012 03:20 PM, Per Förlin wrote: >> Hi Konstantin, >> >> On 11/01/2012 03:40 PM, Konstantin Dorfman wrote: >>> When current request is running on the bus and if next request fetched >>> by mmcqd is NULL, mmc context (mm

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

2012-11-08 Thread Jaehoon Chung
Hi Maya, Thank you for reply. I will check the patch v1 and share the result. Best Regards, Jaehoon Chung On 11/08/2012 09:51 PM, me...@codeaurora.org wrote: > Hi Jaehoon, > > While sending patch V2 the wrong version was sent, that doen't include the > lock. > This causes the crash that you hav

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

2012-11-08 Thread merez
Hi Jaehoon, While sending patch V2 the wrong version was sent, that doen't include the lock. This causes the crash that you have seen. Konstantin is currently at the Linux Embedded Conference and would be able to send the new patch only early next week. Until then you can use patch V1 to check the

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

2012-11-08 Thread Jaehoon Chung
Hi, I tested with this patch. But i got some problem. So i want to get your opinion. I used eMMC4.5 card, and using ddr mode, dw-mmc controller. Also use the post/pre-request() in controller. Then i got this message every time. [7.735520] mmc0: new request while areq = eda3046c What's wrong

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

2012-11-06 Thread Jaehoon Chung
Hi Konstantin, On 11/01/2012 11:40 PM, 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 completes. This means if new request comes in while > the mmcqd thread i

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

2012-11-04 Thread Jaehoon Chung
Hi Konstantin, On 11/05/2012 03:20 PM, Per Förlin wrote: > Hi Konstantin, > > On 11/01/2012 03:40 PM, 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 comple

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

2012-11-04 Thread Per Förlin
Hi Konstantin, On 11/01/2012 03:40 PM, 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 completes. This means if new request comes in while > the mmcqd thread i

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

2012-11-01 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 if new request comes in while the mmcqd thread is blocked, this new request can not be prepared in parallel to current ong