From: Jens Axboe <jaxboe@fusionio.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: "James.Bottomley@hansenpartnership.com"
<James.Bottomley@hansenpartnership.com>,
"christof.schmitt@de.ibm.com" <christof.schmitt@de.ibm.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Limit number of integrity segments
Date: Fri, 10 Sep 2010 14:04:03 +0200 [thread overview]
Message-ID: <4C8A1EB3.7020101@fusionio.com> (raw)
In-Reply-To: <1284096730-13147-1-git-send-email-martin.petersen@oracle.com>
On 2010-09-10 07:32, Martin K. Petersen wrote:
>
> [My script defaulted to Jens' old address. Sorry about the repost]
>
> First patch moves min_not_zero() to kernel.h. It's currently defined
> several places throughout the block layer and I was about to introduce
> another instance. So let's make this generic.
>
> Second patch works around the limitations in the zfcp hardware by
> introducing a limit on the number of integrity scatterlist elements.
> Christof will post a separate patch that updates the zfcp driver to take
> advantage of this.
>
> I'd prefer we if could feed everything, including the SCSI changes,
> through the block tree. I have had to change some existing interfaces
> so a post-merge tree will not cut it and compatibility wrappers seem
> like an overkill for this.
So this is a bug and we want to fix it, but it's not a strict
regression against earlier releases. So based on that .37 should
be fine. But there's definitely some reasons for shoving it into
.35 as well. What was your intention?
--
Jens Axboe
next prev parent reply other threads:[~2010-09-10 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 5:32 Limit number of integrity segments Martin K. Petersen
2010-09-10 5:32 ` [PATCH 1/2] Consolidate min_not_zero Martin K. Petersen
2010-09-10 13:20 ` Rolf Eike Beer
2010-09-10 5:32 ` [PATCH 2/2] block/scsi: Provide a limit on the number of integrity segments Martin K. Petersen
2010-09-10 11:45 ` [PATCH] zfcp: Report scatter gather limit for DIX protection information Christof Schmitt
2010-09-10 12:04 ` Jens Axboe [this message]
2010-09-10 12:41 ` Limit number of integrity segments Martin K. Petersen
2010-09-10 12:52 ` Christof Schmitt
2010-09-10 13:01 ` Jens Axboe
2010-09-10 13:17 ` Christof Schmitt
2010-09-10 13:40 ` Jens Axboe
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=4C8A1EB3.7020101@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=christof.schmitt@de.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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.