linux-kernel - Re: [RFC PATCH] block: change max_segments default to USHRT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <yq1mxbehkt6.fsf@sermon.lab.mkp.net>
Date:	Tue, 29 Nov 2011 12:59:01 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Mike Snitzer <snitzer@...hat.com>
Cc:	linux-kernel@...r.kernel.org, Jens Axboe <jaxboe@...ionio.com>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Shuichi Ihara <sihara@....com>
Subject: Re: [RFC PATCH] block: change max_segments default to USHRT_MAX

>>>>> "Mike" == Mike Snitzer <snitzer@...hat.com> writes:

Mike> The reported problem was that a DM multipath device's max_segemnts
Mike> was constrained to BLK_MAX_SEGMENTS (128) even though the
Mike> underlying paths' max_segments were larger.  For example, SCSI
Mike> establishes a max_segments of SCSI_MAX_SG_CHAIN_SEGMENTS (2048).

I'd rather that we revisited the patches I posted a while back where we
have different defaults for LLDs and stacking drivers.

I'll freshen those up and post them later today. I have a few concalls
to clear first...

-- 
Martin K. Petersen	Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/