Date: Sun, 7 Jan 2001 09:52:39 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: memalign and valloc patch
In-Reply-To: <3A57B8D1.31037.75E7A8@localhost>
Message-ID: <Pine.SUN.3.91.1010107094814.21289L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 7 Jan 2001, Mark E. wrote:

> + This function is just like @code{malloc} (@pxref{malloc}) except that the
> + returned pointer is always aligned to a CPU page boundary.

I suggest to tell explicitly what size is our page.  Users might not know 
that.

> + This function is just like @code{malloc} (@pxref{malloc}) except that the
> + returned pointer is always a multiple of @var{alignment}.

Perhaps it is better to say that the pointer is aligned on a boundary 
that is a multiple of @var{alignment}, and explain in a few words what 
alignment is.  Alignment is a tricky notion, and some users might not be
in the know.

Thanks for working on this.