[parsec-users] Dedup Memory allocation

Kotecha, Grishma grishma.kotecha at intel.com
Tue Aug 4 17:12:28 EDT 2009

If this mail is duplicated, please ignore the mail which came from gmail-id. I thought the mail I sent from my Intel Id got bounced.

From: parsec-users-bounces at lists.cs.princeton.edu [mailto:parsec-users-bounces at lists.cs.princeton.edu] On Behalf Of Kotecha, Grishma
Sent: Tuesday, August 04, 2009 2:06 PM
To: parsec-users at lists.cs.princeton.edu
Subject: [parsec-users] Dedup Memory allocation


Following is the definition of MAXBUF (defined in file "dedupdef.h" )

#define MAXBUF (600*1024*1024)     /* 128 MB for buffers */

In bracket it is written 128 MB but figure comes out to be 600MB. Is this a bug or it means something else?

Because of this the malloc function in encoder.c fails. See the following comment:

Enoder.c, Line 652

  u_char * src = (u_char *)malloc(MAXBUF*2);  --> Succeeds
  u_char * left = (u_char *)malloc(MAXBUF);   --> Memory allocation fails here
  u_char * new = (u_char *) malloc(MAXBUF); --> Fails here . Not enough memory to assign.

In 32 bit systems application gets max 2 GB memory. The above three statements exceeds 2 GB limit.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/parsec-users/attachments/20090804/0a819410/attachment.html>

More information about the parsec-users mailing list