| 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
| ||
|
Date: Wed, 23 May 2007 10:18:14 -0500 From: James Bottomley <James.Bottomley@...elEye.com> To: Aubrey Li <aubreylee@...il.com> Cc: Christoph Lameter <clameter@....com>, Bernhard Walle <bwalle@...e.de>, linux-scsi@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] [scsi] Remove __GFP_DMA On Wed, 2007-05-23 at 10:41 +0800, Aubrey Li wrote: > On 5/23/07, Christoph Lameter <clameter@....com> wrote: > > On Mon, 21 May 2007, Bernhard Walle wrote: > > > > > [PATCH] [scsi] Remove __GFP_DMA > > > > > > After 821de3a27bf33f11ec878562577c586cd5f83c64, it's not necessary to alloate a > > > DMA buffer any more in sd.c. > > > > > > Signed-off-by: Bernhard Walle <bwalle@...e.de> > > > > Great that avoids a DMA kmalloc slab. Any other GFP_DMAs left in the scsi > > layer? > > > > Acked-by: Christoph Lameter <clameter@....com> > > Yes, here is another patch I'll defer to Mark on this one. However, please remember that you can't just blindly remove GFP_DMA ... there are some cards which require it. Aacraid is one example ... it has a set of cards that can only DMA to 31 bits. For them, the GFP_DMA is necessary: The allocation in question is a scatterlist, which must be within the device DMA mask. James - 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/
Powered by blists - more mailing lists