[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090515181641.GB15360@parisc-linux.org>
Date: Fri, 15 May 2009 12:16:41 -0600
From: Matthew Wilcox <matthew@....cx>
To: "Mukker, Atul" <Atul.Mukker@....com>
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
On Fri, May 15, 2009 at 12:03:39PM -0600, Mukker, Atul wrote:
> > 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.
I'd stick to the C APIs where possible ... oh, that's what Linux does. OK ;-)
> > 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."
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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