All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
To: linux-block@vger.kernel.org
Cc: Mateusz Nowak <mateusz.nowak@intel.com>, linux-mmc@vger.kernel.org
Subject: [PATCH 0/2] mmc, block: override default max_dev_sectors
Date: Wed,  2 Mar 2016 09:54:15 +0100	[thread overview]
Message-ID: <cover.1456847028.git.pawelx.wodkowski@intel.com> (raw)

From: Mateusz Nowak <mateusz.nowak@intel.com>

commit ca369d51b3e1 ("block/sd: Fix device-imposed transfer length limits")
introduced max_dev_sectors as upper limit for max_hw_sectors. This caused
limitation of maximum block size to default max_dev_sectors value - 127,
causing performance degradation with higher block sizes.

This patchset is allowing mmc driver to override max_dev_sectors value.

Cc: linux-mmc@vger.kernel.org
Mateusz Nowak (2):
  block: Allow to set max_dev_sectors for a queue.
  mmc/block: Override default max_dev_sectors.

 block/blk-settings.c     | 24 ++++++++++++++++++++++++
 drivers/mmc/card/queue.c | 10 ++++++++++
 include/linux/blkdev.h   |  1 +
 3 files changed, 35 insertions(+)

-- 
1.9.1


             reply	other threads:[~2016-03-02  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  8:54 Pawel Wodkowski [this message]
2016-03-02  8:55 ` [PATCH 1/2] block: Allow to set max_dev_sectors for a queue Pawel Wodkowski
2016-03-02  8:55 ` [PATCH 2/2] mmc/block: Override default max_dev_sectors Pawel Wodkowski
2016-03-02 17:12 ` [PATCH 0/2] mmc, block: override " Christoph Hellwig
2016-03-04 10:49   ` Nowak, Mateusz
2016-03-05 21:58     ` Martin K. Petersen

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=cover.1456847028.git.pawelx.wodkowski@intel.com \
    --to=pawelx.wodkowski@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mateusz.nowak@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.