linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maya Erez <merez@codeaurora.org>
To: linux-mmc@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, Maya Erez <merez@codeaurora.org>
Subject: [PATCH v1 0/1] mmc: block: Add write packing control
Date: Sun, 20 May 2012 22:10:33 +0300	[thread overview]
Message-ID: <1337541034-11125-1-git-send-email-merez@codeaurora.org> (raw)

Our experiments showed that the write packing causes degradation of the read 
throughput, in parallel read and write operations.
Since the read latency is critical for user experience we added a write packing control 
mechanism that disables the write packing in case of read requests.
This will ensure that read requests latency is not increased due to long write packed commands.

The trigger for enabling the write packing is managing to pack several write requests. 
The number of potential packed requests that will trigger the packing can be configured via sysfs.
The trigger for disabling the write packing is a fetch of a read request.

this patch is dependant in the following patches:
  [PATCH v6 1/3] mmc: core: Add packed command feature of eMMC4.5
  [PATCH v6 2/3] mmc: core: Support packed write command for eMMC4.5 device

Maya Erez (1):
  mmc: block: Add write packing control

 drivers/mmc/card/block.c |   44 ++++++++++++++++++++++++++++++++++++++
 drivers/mmc/card/queue.c |    2 +
 drivers/mmc/card/queue.h |    2 +
 drivers/mmc/core/host.c  |   52 ++++++++++++++++++++++++++++++++++++++++++++++
 include/linux/mmc/host.h |    5 +++-
 5 files changed, 104 insertions(+), 1 deletions(-)

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


             reply	other threads:[~2012-05-20 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 19:10 Maya Erez [this message]
2012-05-20 19:10 ` [PATCH v1 1/1] mmc: block: Add write packing control Maya Erez

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=1337541034-11125-1-git-send-email-merez@codeaurora.org \
    --to=merez@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    /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).