All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Bottomley <jbottomley@parallels.com>,
	linux-scsi@vger.kernel.org, Vasu Dev <vasu.dev@linux.intel.com>
Subject: Re: [PATCH] fcoe: Reduce max_sectors to 1024
Date: Wed, 09 Jul 2014 08:40:30 +0200	[thread overview]
Message-ID: <53BCE3DE.6000605@suse.de> (raw)
In-Reply-To: <20140709061838.GA28335@infradead.org>

On 07/09/2014 08:18 AM, Christoph Hellwig wrote:
> 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.
>
ixgbe can handle up to 256 sgl elements, but the maximum single I/O 
size is 256 pages. This translates into 1024 sectors.

And seeing that the 'fcoe' driver is effectively tied to ixgbe ATM I 
doubt it's worth investing in yet another callout here.
Intel, can you clarify on i40e? Is it FCoE capable?
If so it might be worth adding a configuration knob here.
Unless i40e has the same limitations as ixgbe ...

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-07-09  6:40 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 [this message]
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=53BCE3DE.6000605@suse.de \
    --to=hare@suse.de \
    --cc=hch@infradead.org \
    --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 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.