Re: Limit number of integrity segments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux