public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Pawel Wodkowski <pawelx.wodkowski@intel.com>
Cc: linux-block@vger.kernel.org,
	Mateusz Nowak <mateusz.nowak@intel.com>,
	linux-mmc@vger.kernel.org
Subject: Re: [PATCH 0/2] mmc, block: override default max_dev_sectors
Date: Wed, 2 Mar 2016 09:12:28 -0800	[thread overview]
Message-ID: <20160302171227.GA5229@infradead.org> (raw)
In-Reply-To: <cover.1456847028.git.pawelx.wodkowski@intel.com>

On Wed, Mar 02, 2016 at 09:54:15AM +0100, Pawel Wodkowski wrote:
> 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.

Past commit 5f009d ("block: Initialize max_dev_sectors to 0"), this
should not be needed.

  parent reply	other threads:[~2016-03-02 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02  8:54 [PATCH 0/2] mmc, block: override default max_dev_sectors Pawel Wodkowski
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 ` Christoph Hellwig [this message]
2016-03-04 10:49   ` [PATCH 0/2] mmc, block: override " 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=20160302171227.GA5229@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mateusz.nowak@intel.com \
    --cc=pawelx.wodkowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox