linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ashwin Rao <ashwin_s_rao@yahoo.com>
To: Valdis.Kletnieks@vt.edu, haveblue@us.ibm.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Atomic operation for physically moving a page (for memory defragmentation)
Date: Fri, 18 Jun 2004 20:15:36 -0700 (PDT)	[thread overview]
Message-ID: <20040619031536.61508.qmail@web10902.mail.yahoo.com> (raw)
In-Reply-To: <200406190103.i5J13WWr010687@turing-police.cc.vt.edu>

--- Valdis.Kletnieks@vt.edu wrote:
> On Fri, 18 Jun 2004 17:37:12 PDT, Ashwin Rao
>said:
> > I want to copy a page from one physical location
> to
> > another (taking the appr. locks).
> 
> At the risk of sounding stupid, what problem are you
> trying to solve by copying
> a page? Not only (as you note) could the page be
> referenced by multiple
> processes, it could (conceivably) belong to a kernel
> slab or something, or be a
> buffer for an in-flight I/O request, or any number
> of other possibly-racy
> situations.
> 

The problem is the memory fragmentation. The code i am
writing is for the memory defragmentation as proposed
by Daniel Phillips, my project partner Alok mooley has
given mailed a simple prototype in the mid of feb.

> If it's only a specific *type* of page, or
> explaining why you're trying to do
> it, or what timing/etc constraints you have (if it's
> a sufficiently rare(*) case,
> it might make sense to just grab the BKL and copy
> the page with a memcpy().)
> 

The pages in the LRU list are selected. As these pages
can be swapped they can moved to another location in
the memory.

> (*) Yes, I know the BKL isn't something you want to
> grab if you can help it.

Isnt it a bad idea to take the BKL, the performance of
SMP systems will drastically be hampered.

> However, if we're on an unlikely error path or
> similar and other options aren't suitable...
The way we work is as follows
Initially a block is selected which can be moved i.e
pages on lru or free and the pages are moved to a
suitable free pages. The main problem arises during
the copying and updation process. All the ptes are to
updates. a method similar to try_to_unmap_one  is used
to identify the ptes and the physical address is
updated.

Maintaining atomicity in uniprocessor systems is easy
by preempt_enable and preempt_disable during the
operation. This implementation cannot be used for SMP
systems. 
Now during the time a page is copied/updatede if a
page is accessed the copied contents become invalid,
as updation is not done. Also during updation a
similar situation might arise.
The problem we are facing is to maintain the atomicity
of this operation on SMP boxes.

Ashwin


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 
--
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>

  parent reply	other threads:[~2004-06-19  3:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-19  0:37 Atomic operation for physically moving a page Ashwin Rao
2004-06-19  1:03 ` Valdis.Kletnieks
2004-06-19  2:53   ` Dave Hansen
2004-06-19  3:15   ` Ashwin Rao [this message]
2004-06-19  3:34     ` Atomic operation for physically moving a page (for memory defragmentation) Valdis.Kletnieks
2004-06-19  4:25     ` Dave Hansen
2004-06-23  9:04       ` IWAMOTO Toshihiro
2004-06-23 11:59       ` Hirokazu Takahashi
2004-06-23 20:56         ` Dave Hansen
2004-06-24  7:19           ` IWAMOTO Toshihiro
2004-06-24 11:31             ` Dave Hansen
2004-06-23 10:32     ` Hirokazu Takahashi
2004-06-19  2:43 ` Atomic operation for physically moving a page Dave Hansen

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=20040619031536.61508.qmail@web10902.mail.yahoo.com \
    --to=ashwin_s_rao@yahoo.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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