linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merez@codeaurora.org
Cc: merez@codeaurora.org, Jaehoon Chung <jh80.chung@samsung.com>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	Chris Ball <cjb@laptop.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Hanumath Prasad <hanumath.prasad@stericsson.com>,
	Per FORLIN <per.forlin@stericsson.com>,
	Sebastian Rasmussen <sebras@gmail.com>,
	"Dong, Chuanxiao" <chuanxiao.dong@intel.com>,
	"svenkatr@ti.com" <svenkatr@ti.com>,
	Saugata Das <saugata.das@linaro.org>,
	Konstantin Dorfman <kdorfman@codeaurora.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ulf Hansson <ulf.hansson@stericsson.com>
Subject: Re: [PATCH v9] mmc: support BKOPS feature for eMMC
Date: Tue, 12 Jun 2012 23:18:11 -0700 (PDT)	[thread overview]
Message-ID: <63d2a1617cbe83b94750378ebe64520e.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <4FD803E0.8050206@samsung.com>


On Tue, June 12, 2012 8:07 pm, Jaehoon Chung wrote:
> On 06/12/2012 07:58 PM, merez@codeaurora.org wrote:
>
>>> @@ -359,12 +443,15 @@ struct mmc_async_req *mmc_start_req(struct
>> mmc_host
>>> *host,
>>>  	if (!err && areq)
>>>  		start_err = __mmc_start_req(host, areq->mrq);
>>>
>>> -	if (host->areq)
>>> +	if (host->areq) {
>>> +		if (!areq && host->areq && mmc_card_mmc(host->card))
>>> +			mmc_start_bkops(host->card);
>> I think it would be better to start tey BKOPs in the queue thread when
>> it
>> becomes idle.
>> We have seen cases where there are several requests fetched and then
>> NULL
>> but by the time the previous request ends there are more requests to be
>> fetched. Starting the BKOPs here instead of in the queue thread
>> increases
>> the probability of using HPI to stop the BKOPs due to incoming request,
>> which is not a desirable action.
>
> I will change this point.
>
>>
>>>  		mmc_post_req(host, host->areq->mrq, 0);
>>> +	}
>>>
>>>  	 /* Cancel a prepared request if it was not started. */
>>>  	if ((err || start_err) && areq)
>>> -			mmc_post_req(host, areq->mrq, -EINVAL);
>>> +		mmc_post_req(host, areq->mrq, -EINVAL);
>> Remove this change, it is not related to this patch.
>
> Ok.
> Anything else?
>
> Best Regards,
> Jaehoon Chung
We have no further comments.

Thanks,
Maya Erez

-- 
Sent by consultant of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum


  reply	other threads:[~2012-06-13  6:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 10:58 [PATCH v9] mmc: support BKOPS feature for eMMC merez
2012-06-13  3:07 ` Jaehoon Chung
2012-06-13  6:18   ` merez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-08  4:39 Jaehoon Chung
2012-06-13 12:40 ` Dong, Chuanxiao
     [not found]   ` <17296D9F8FF2234F831FC3DF505A87A90FEA11E5@SHSMSX102.ccr.corp.intel.com >
2012-06-14 14:49     ` Konstantin Dorfman
2012-06-15  3:00   ` Jaehoon Chung
2012-06-13 13:53 ` S, Venkatraman
2012-06-14  8:44   ` merez
2012-06-15  4:29   ` Jaehoon Chung
2012-06-14 13:46 ` Adrian Hunter
2012-06-14 14:58   ` Konstantin Dorfman
2012-07-12  5:02   ` Jaehoon Chung
2012-07-12  6:00     ` Adrian Hunter
2012-07-12  6:50       ` Jaehoon Chung
     [not found] ` <4FD88B7D.3000600@codeaurora.org>
2012-06-15  4:19   ` Jaehoon Chung
2012-06-15  6:10     ` Subhash Jadavani
2012-07-06 16:47 ` Chris Ball
2012-07-08 10:13   ` merez
2012-07-09  2:34     ` Jaehoon Chung
2012-07-09  2:48       ` Chris Ball
2012-07-09  4:14         ` Jaehoon Chung
2012-07-09  4:39           ` Chris Ball

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63d2a1617cbe83b94750378ebe64520e.squirrel@www.codeaurora.org \
    --to=merez@codeaurora.org \
    --cc=adrian.hunter@intel.com \
    --cc=chuanxiao.dong@intel.com \
    --cc=cjb@laptop.org \
    --cc=hanumath.prasad@stericsson.com \
    --cc=jh80.chung@samsung.com \
    --cc=kdorfman@codeaurora.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=saugata.das@linaro.org \
    --cc=sebras@gmail.com \
    --cc=svenkatr@ti.com \
    --cc=ulf.hansson@stericsson.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).