From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"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 08:41:27 -0400 [thread overview]
Message-ID: <yq1k4mtrcso.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4C8A1EB3.7020101@fusionio.com> (Jens Axboe's message of "Fri, 10 Sep 2010 14:04:03 +0200")
>>>>> "Jens" == Jens Axboe <jaxboe@fusionio.com> writes:
Jens> So this is a bug and we want to fix it, but it's not a strict
Jens> regression against earlier releases. So based on that .37 should
Jens> be fine. But there's definitely some reasons for shoving it into
Jens> .35 as well. What was your intention?
I was aiming at 2.6.37 since it's a pretty big change to wedge in this
late in the .36 cycle. And the zfcp DIX support is only experimental.
But that's really Christof's call. My concern wrt. 2.6.36 is purely
process-related, I don't have any technical objections.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2010-09-10 12:42 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 ` Limit number of integrity segments Jens Axboe
2010-09-10 12:41 ` Martin K. Petersen [this message]
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=yq1k4mtrcso.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=christof.schmitt@de.ibm.com \
--cc=jaxboe@fusionio.com \
--cc=linux-scsi@vger.kernel.org \
/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.