[8472] in linux-scsi channel archive
Re: scsi_init_malloc and scsi_malloc
daemon@ATHENA.MIT.EDU (Drew Eckhardt)
Thu Mar 23 18:07:03 2000
Message-Id: <200003232304.QAA11008@chopper.Poohsticks.ORG>
To: "Eric Youngdale" <eric@andante.org>
Cc: "Stanley Wu" <wudragon2@yahoo.com>,
"scsi" <linux-scsi@vger.rutgers.edu>
In-reply-to: Your message of "Thu, 23 Mar 2000 16:54:08 EST."
<004301bf9512$50905750$4d0310ac@fairfax.datafocus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <11005.953852668.1@chopper.Poohsticks.ORG>
Date: Thu, 23 Mar 2000 16:04:28 -0700
From: Drew Eckhardt <drew@Poohsticks.Org>
In message <004301bf9512$50905750$4d0310ac@fairfax.datafocus.com>, eric@andante
.org writes:
> scsi_malloc() is really only to be used in allocating DMA-safe memory
>for bounce buffers and other such structures.
>
> scsi_init_malloc() is essentially just a wrapper around kmalloc().
scsi_init_malloc() existed because I wanted SCSI device allocation to be
entirely dynamic, and in early Linux, kmalloc() didn't work until after
the drivers had initialized.
>you just need some general purpose memory, use kmalloc(). In the 2.3 series
>kernel there is no longer a scsi_init_malloc() function - everything that
>used it now uses kmalloc instead.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
