public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hideki Yamamoto" <hideki@hpc.bs1.fc.nec.co.jp>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Pagesize is different between IA32 and IA64
Date: Mon, 12 Nov 2001 08:15:53 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805465@msgid-missing> (raw)

 Hello all.

 If this problem has already known, I am sorry.

 I am investigating the problem that calloc returns no
 cleared area.
 It was made on IA32 system and executes on IA64.
 I think calloc expects to clear the memories sbrk
 returned. But When the program made on IA32 is
 executing on IA64 system, sbrk sometimes returns no
 cleared area. 
 Because the Kernel on IA64 alignes the memories 16K
 bytes. However, when the progmam made on IA32 is
 executing on IA64, the function __getpagesize returns
 4Kbytes. At this case, if the memories that calloc
 requests to return sbrk(-xxx) is smaller than
 16Kbytes, the kernel do not unmap this memory.
 (I think that the time that the memories clears 0 by
 the kernel is when the kernel maps memories by the signal) 

 How do you think?

--
Regards, 
Hideki Yamamoto   (V).v.(V) # Empowered by Innovation



             reply	other threads:[~2001-11-12  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-12  8:15 Hideki Yamamoto [this message]
2001-11-12 15:28 ` [Linux-ia64] Pagesize is different between IA32 and IA64 n0ano
2001-11-12 23:58 ` David Mosberger
2001-11-13  4:58 ` 
2001-11-13 15:15 ` n0ano
2001-11-14  6:16 ` Dugger's
2001-11-14  6:43 ` Dugger's
2001-11-14  6:53 ` Hideki Yamamoto
2001-11-14  7:00 ` Hideki Yamamoto
2001-11-15 15:33 ` n0ano
2001-11-16  6:17 ` miyoshi
2001-11-16 15:09 ` n0ano
2001-11-22  6:48 ` miyoshi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590698805465@msgid-missing \
    --to=hideki@hpc.bs1.fc.nec.co.jp \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox