All of lore.kernel.org
 help / color / mirror / Atom feed
From: vamsi krishna <vamsi.krishnak@gmail.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Bhanu Kalyan Chetlapalli <chbhanukalyan@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Whats in this vaddr segment 0xffffe000-0xfffff000 ---p ?
Date: Fri, 22 Jul 2005 23:26:58 +0530	[thread overview]
Message-ID: <3faf056805072210563ed8f158@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507221154150.16740@chaos.analogic.com>

Hi,

> It doesn't. The 32-bit machines never show 64 bit words in
> /proc/NN/maps. They don't "know" how.
> 
> b7fd6000-b7fd7000 rw-p b7fd6000 00:00 0
> b7ff5000-b7ff6000 rw-p b7ff5000 00:00 0
> bffe1000-bfff6000 rw-p bffe1000 00:00 0          [stack]
> ffffe000-fffff000 ---p 00000000 00:00 0          [vdso]
> ^^^^^^^^____________ 32 bits

hello john can you tell me what is [vdso], does it have any content
related file descriptor table it seems that the if I dont save this
segment during checkpointing,  the file open descriptors (i.e FILE *)
seems to have null after restoration.

Sincerely appreciate your inputs.

Cheers!
Vamsi

  reply	other threads:[~2005-07-22 17:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  6:25 Whats in this vaddr segment 0xffffe000-0xfffff000 ---p ? vamsi krishna
2005-07-22  7:46 ` Jan Engelhardt
2005-07-22 14:27 ` Bhanu Kalyan Chetlapalli
2005-07-22 15:18   ` vamsi krishna
2005-07-22 15:56     ` linux-os (Dick Johnson)
2005-07-22 17:56       ` vamsi krishna [this message]
2005-07-22 19:32         ` linux-os (Dick Johnson)
2005-07-22 21:07           ` vamsi krishna
2005-07-22 23:30           ` Jirka Kosina

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=3faf056805072210563ed8f158@mail.gmail.com \
    --to=vamsi.krishnak@gmail.com \
    --cc=chbhanukalyan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.