> -----Original Message----- > From: Matthew Wilcox [mailto:matthew@xxxxxx] > Sent: Friday, May 15, 2009 12:36 PM > To: Mukker, Atul > Cc: Jeff Garzik; Julian Calaby; adam radford; linux- > kernel@xxxxxxxxxxxxxxx; Austria, Winston; linux-scsi@xxxxxxxxxxxxxxx > Subject: Re: [RFQ] New driver architecture questions > > On Fri, May 15, 2009 at 08:56:25AM -0600, Mukker, Atul wrote: > > [Atul] I think we are close, for example, memcpy API in the stack is > osi_memcpy(), which translates to memcpy() on Linux and > ScsiPortMoveMemory() on windows. > > The solution to "We have some people who speak French and other people who > speak German" is not to invent Esperanto ;-) [Atul] We really wish they could communicate in English :-), since that's not an option, we agree in principle that using native Linux Kernel APIs wherever possible is probably a good idea. > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
