From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <jbottomley@parallels.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org, Vasu Dev <vasu.dev@linux.intel.com>
Subject: Re: [PATCH] fcoe: Reduce max_sectors to 1024
Date: Tue, 8 Jul 2014 23:18:38 -0700 [thread overview]
Message-ID: <20140709061838.GA28335@infradead.org> (raw)
In-Reply-To: <1404886581-3218-1-git-send-email-hare@suse.de>
On Wed, Jul 09, 2014 at 08:16:21AM +0200, Hannes Reinecke wrote:
> The DDP offload on ixgbe is only capable of handling requests up
> to 1024 sectors. So we should be exposing this to avoid spurious
> messages about 'not enough user buffers'.
Shouldn't the network driver be able to communicate it's offload
capabilities to the fcoe core? I'd be happy to take this as an iterim
fix if there's a comment explaining it, but long-term it should be
driver specific.
next prev parent reply other threads:[~2014-07-09 6:18 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 [this message]
2014-07-09 6:40 ` Hannes Reinecke
2014-07-09 18:58 ` Vasu Dev
2014-07-10 6:36 ` Christoph Hellwig
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=20140709061838.GA28335@infradead.org \
--to=hch@infradead.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