[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6C678488C5CEE74F813A4D1948FD2DC7A96C787D@cosmail02.lsi.com>
Date: Fri, 15 May 2009 12:38:40 -0600
From: "Mukker, Atul" <Atul.Mukker@....com>
To: Matthew Wilcox <matthew@....cx>
CC: Jeff Garzik <jeff@...zik.org>,
Julian Calaby <julian.calaby@...il.com>,
adam radford <aradford@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Austria, Winston" <Winston.Austria@....com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: RE: [RFQ] New driver architecture questions
> > > Using one or the other internally is fine (we don't care what you do),
> > > but we want to see memcpy(). By the way, the documentation I found
> for
> > > ScsiPortMoveMemory() seems to indicate that it's memmove(), not
> memcpy().
> > > Mapping memcpy() to ScsiPortMoveMemory() is fine ... but you can't
> > > realiably go the other way.
> > [Atul] It's actually memcpy(),http://msdn.microsoft.com/en-
> us/library/ms805434.aspx
>
> No, it's memmove(). "The (ReadBuffer + Length) can overlap the area
> pointed to by WriteBuffer."
[Atul] Look, you are already figuring out possible issues with the source code without it being out yet :-).
Thanks everyone for your inputs so far!
Atul
--
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