From: Anton Blanchard <anton@samba.org>
To: Mel <mel@csn.ul.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vmalloc comments patch
Date: Sun, 21 Apr 2002 09:47:52 +1000 [thread overview]
Message-ID: <20020420234752.GA26727@krispykreme> (raw)
In-Reply-To: <Pine.LNX.4.44.0204201740480.3995-100000@skynet>
Hi,
> + * To give a safety margin, the linear address starts about 8MB after the end
> + * of physical memory at VMALLOC_START. This is to try and catch memory
> + * overruns.
Thats architecture dependent. On ppc64 for example the kernel text
starts at 0xC000000000000000 and the vmalloc region starts at
0xD000000000000000, 2^60 bits apart.
> + /* The page table is unlocked because we don't need to traverse
> + * the page tables while a page is been allocated. As
> + * alloc_page could block for a long time, let go the lock
> + */
> spin_unlock(&init_mm.page_table_lock);
> page = alloc_page(gfp_mask);
> spin_lock(&init_mm.page_table_lock);
Since alloc_page can sleep we must drop the spinlock.
Anton
next prev parent reply other threads:[~2002-04-20 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 18:37 vmalloc comments patch Mel
2002-04-20 23:47 ` Anton Blanchard [this message]
2002-04-21 20:54 ` Mel
2002-04-21 14:09 ` Daniel Phillips
2002-04-22 16:52 ` Mel
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=20020420234752.GA26727@krispykreme \
--to=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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