linux-kernel - RE: [PATCH -mm 11/11] aacraid: use pci_set_dma_max_seg

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: <AE4F746F2AECFC4DA4AADD66A1DFEF01F3DAB5@otce2k301.adaptec.com>
Date:	Wed, 24 Oct 2007 09:34:25 -0400
From:	"Salyzyn, Mark" <mark_salyzyn@...ptec.com>
To:	"Jeff Garzik" <jeff@...zik.org>, "FUJITA Tomonori" <tomof@....org>
Cc:	<akpm@...ux-foundation.org>, <linux-kernel@...r.kernel.org>,
	<linux-scsi@...r.kernel.org>, <James.Bottomley@...elEye.com>,
	"AACRAID" <aacraid@...ptec.com>, <fujita.tomonori@....ntt.co.jp>
Subject: RE: [PATCH -mm 11/11] aacraid: use pci_set_dma_max_seg_size

Jeff Garzik [mailto:jeff@...zik.org] writes:
> is this needed, given that the default is already 65536?

Apparently so, as we had to add it in the past, mainly because the
feature to limit was not part of the SCSI layer when the original limit
code was added. At that time it replaced a complicated sg breakup
algorithm.

Does your statement guarantee that the default will not change to a
large value? If not, then we need to enforce it in perpetuity...

Sincerely -- Mark Salyzyn
-
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/