linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Anand Eswaran" <aeswaran@andrew.cmu.edu>
To: linux-mm@kvack.org
Subject: Doubt in do_no_page()
Date: Wed, 21 Jan 2004 10:47:19 -0500 (EST)	[thread overview]
Message-ID: <2276.128.2.181.129.1074700039.squirrel@webmail.andrew.cmu.edu> (raw)

Hi all :

  I have a doubt regarding the do_no_page function in memory.c. I would
greatly appreciate it if someone could help me out.


My questions are appended ( they're between the lines ) near the
corresponding code of concern.





int do_no_page(struct mm_struct * mm,
	               struct vm_area_struct * vma,
	               unsigned long address,
	               int write_access,
	               pte_t *page_table)


	struct page * new_page;
	pte_t entry;

	if (!vma->vm_ops || !vma->vm_ops->nopage)
		return do_anonymous_page(mm, vma, page_table, write_access, address);

QUESTION
------------------------------------------------------------------------

 I assume that most faults would be serviced by the do_anonymous page i.e
for most "normal" vma's ( say heap ) the vma->vm_ops->nopage would be
NULL. Is that true?


------------------------------------------------------------------------

	spin_unlock(&mm->page_table_lock);

	new_page = vma->vm_ops->nopage(vma, address & PAGE_MASK, 0);

	if (new_page == NULL)	/* no page was available -- SIGBUS */
		return 0;
	if (new_page == NOPAGE_OOM)
		return -1;


QUESTION
-----------------------------------------------------------------------

1) What type of vma's come here ?
------------------------------------------------------------------------



	/*
	 * Should we do an early C-O-W break?
	 */
	if (write_access && !(vma->vm_flags & VM_SHARED)) {
		struct page * page = alloc_page(GFP_HIGHUSER);
		if (!page) {
			page_cache_release(new_page);
			return -1;
		}
		copy_user_highpage(page, new_page, address);
		page_cache_release(new_page);
		lru_cache_add(page);
		new_page = page;
	}

	spin_lock(&mm->page_table_lock);
	/*
	 * This silly early PAGE_DIRTY setting removes a race
	 * due to the bad i386 page protection. But it's valid
	 * for other architectures too.
	 *
	 * Note that if write_access is true, we either now have
	 * an exclusive copy of the page, or this is a shared mapping,
	 * so we can make it writable and dirty to avoid having to
	 * handle that later.
	 */
	/* Only go through if we didn't race with anybody else... */
	if (pte_none(*page_table)) {
		++mm->rss;
		flush_page_to_ram(new_page);
		flush_icache_page(vma, new_page);
		entry = mk_pte(new_page, vma->vm_page_prot);
		if (write_access)
			entry = pte_mkwrite(pte_mkdirty(entry));
		set_pte(page_table, entry);
	} else {
		/* One of our sibling threads was faster, back out. */
		page_cache_release(new_page);
		spin_unlock(&mm->page_table_lock);
		return 1;
	}

	/* no need to invalidate: a not-present page shouldn't be cached */
	update_mmu_cache(vma, address, entry);
	spin_unlock(&mm->page_table_lock);
	return 2;	/* Major fault */




I would greatly appreciate if someone could answer this for me in some depth.

Thanks a lot,
------
Anand.






--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

             reply	other threads:[~2004-01-21 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 15:47 Anand Eswaran [this message]
2004-01-21 16:16 ` logan
2004-01-21 16:35   ` Randy.Dunlap
2004-01-21 17:08     ` logan
2004-01-21 17:11     ` logan
2004-01-21 16:51   ` Anand Eswaran

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=2276.128.2.181.129.1074700039.squirrel@webmail.andrew.cmu.edu \
    --to=aeswaran@andrew.cmu.edu \
    --cc=linux-mm@kvack.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