lkml.org 
[lkml]   [1998]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: write[blw] vs memcpy?
Date
In article <19980405065957.44075@hazel>,
Raul Miller <rdm@test.legislate.com> wrote:
>ralf@uni-koblenz.de <ralf@uni-koblenz.de> wrote:
>
>> Finally there is no need to rely on {read,write}[bwl]. There are special
>> purpose I/O copy functions available, memset_io(), memcpy_fromio() and
>> memcpy_toio() which will do the job efficient and portable.
>
>Oops, I saw those, and foolishly thought that they had to do with io
>port space. [Please: nobody post to tell me just how dumb I was to
>think this: I know that address space is too limited to warrant such
>mechanisms.]

Argh, I agree that maybe the naming isn't the best one. I never even
thought of the confusion issue, but you're right, they are not well
named. I should at least add a comment on this (although they _are_
documented in IO-mapping.txt - maybe we should just make some of the
documentation more well-known).

Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.061 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site