public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Vasu Dev <vasu.dev@linux.intel.com>
Cc: Hannes Reinecke <hare@suse.de>,
	Christoph Hellwig <hch@infradead.org>,
	James Bottomley <jbottomley@parallels.com>,
	linux-scsi@vger.kernel.org, fcoe-devel@open-fcoe.org
Subject: Re: [PATCH] fcoe: Reduce max_sectors to 1024
Date: Wed, 9 Jul 2014 23:36:30 -0700	[thread overview]
Message-ID: <20140710063630.GA13276@infradead.org> (raw)
In-Reply-To: <1404932313.12914.36.camel@vfc0>

Hannes, can you respin the patch with a comment explaining the limit?

> Does it limit IO size for pass through IO not through block layer ? 

The max_sectors limit also limits the size of passthrough requests.


      reply	other threads:[~2014-07-10  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  6:16 [PATCH] fcoe: Reduce max_sectors to 1024 Hannes Reinecke
2014-07-09  6:18 ` Christoph Hellwig
2014-07-09  6:40   ` Hannes Reinecke
2014-07-09 18:58     ` Vasu Dev
2014-07-10  6:36       ` Christoph Hellwig [this message]

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=20140710063630.GA13276@infradead.org \
    --to=hch@infradead.org \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=hare@suse.de \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vasu.dev@linux.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