Skip to contentSkip to conversation

why use memcpy when memmove is there?

DISCUSSION sk malik 4 participants 4 messages Aug 13, 2007 – Aug 14, 2007

lore
Share & tools
lore

sk malik

author
#0 lore raw

Hi, All

We were looking at "[kernel]/lib/string.c"
(http://lxr.linux.no/source/lib/string.c#L500)

memcpy copies a part of memory to some other location but It will not work for all cases of overlapping blocks.(if the start of destination block falls between the source block)

while memove copes with overlapping areas.

then why is memcpy present in the sources can't we simply do

"#define memcpy memmove" in include/linux/string.h

or am I missing something?

Regards
Sri

Unlimited freedom, unlimited storage. Get it now, on http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/

#1 lore raw
Quoted 7 lines · sk malik

Subject: why use memcpy when memmove is there?

memcpy copies a part of memory to some other location but It will not work for all cases of overlapping blocks.(if the start of destination block falls between the source block)

Quoted 8 lines

while memove copes with overlapping areas.

then why is memcpy present in the sources can't we simply do

"#define memcpy memmove" in include/linux/string.h

or am I missing something?

memmove must copy with overlapping memory segments, while memcpy does not, and can therefore use a different optimization strategy. But that would have been apparent if you had looked at the code.

Jan

#2 lore raw
In reply to sk malik
Quoted 5 lines · sk malik

memcpy copies a part of memory to some other location but It will not work for all cases of overlapping blocks.(if the start of destination block falls between the source block)

Quoted 8 lines

while memove copes with overlapping areas.

then why is memcpy present in the sources can't we simply do

"#define memcpy memmove" in include/linux/string.h

or am I missing something?

The restriction that memcpy is undefined for overlapping areas (IOW, is only defined for non-overlapping areas) can be used for optimizations in memcpy which are not possible in memmove. An example, I suppose:
http://lxr.linux.no/source/arch/m68k/lib/string.c#L79
http://lxr.linux.no/source/arch/m68k/lib/string.c#L146

Signature · 3 lines
Stefan Richter
-=====-=-=== =--- -==-=
http://arcgraph.de/sr/
#3 lore raw
In reply to sk malik
Quoted 11 lines

Hi, All

We were looking at "[kernel]/lib/string.c"
(http://lxr.linux.no/source/lib/string.c#L500)

memcpy copies a part of memory to some other location but It will not work for all cases of overlapping blocks.(if the start of destination block falls between the source block)

Quoted 8 lines

while memove copes with overlapping areas.

then why is memcpy present in the sources can't we simply do

"#define memcpy memmove" in include/linux/string.h

or am I missing something?

Suppose you have two vehicles, an economy car and a semi truck. The truck can go everyplace the car can go, and the truck can carry a bigger load. So why would you ever use the car? Answer: The car uses less gas and you don't always need a truck.

Think about what it takes to be able to copy one block of memory to another location when those locations might overlap. You don't always need that.

DS