From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: hugh@veritas.com, haveblue@us.ibm.com, iwamoto@valinux.co.jp,
kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org
Subject: Re: [PATCH] Migration cache
Date: Sat, 23 Oct 2004 17:28:57 -0200 [thread overview]
Message-ID: <20041023192857.GA12334@logos.cnet> (raw)
In-Reply-To: <20041022.154912.129768542.taka@valinux.co.jp>
On Fri, Oct 22, 2004 at 03:49:12PM +0900, Hirokazu Takahashi wrote:
> Hi,
>
> > On Thu, Oct 21, 2004 at 08:09:35PM +0100, Hugh Dickins wrote:
> > > On Thu, 21 Oct 2004, Marcelo Tosatti wrote:
> > > > On Thu, Oct 21, 2004 at 02:10:44AM +0900, Hirokazu Takahashi wrote:
> > > > >
> > > > > I guess it would be better to reserve one swap type for the migration
> > > > > cache instead of reserving the bit to reduce the impact of the maximum
> > > > > number of swap types.
> > >
> > > I thought the same ...
> > >
> > > > By reserving one swap type we would also use a bit. Using a swap type is
> > > > the same thing as using a bit in the swap pagetableentry. (the swap type
> > > > has 5 bits reserved for swap devices, 2^5 = 32 swap devices).
> > >
> > > ... and don't understand your response.
> > >
> > > Reserving a swap type leaves 31 swap devices for normal use, okay;
> > > but reserving a bit leaves only 16 swap devices for normal use.
> >
> > Oh stupid idiot I am! Of course, we can then remove "pte_is_migration"
> > (and all the related pte handling code).
> >
> > Added to TODO list.
> >
> > If anyone wants to contribute that it would be cool cause I'm
> > quite busy with other stuff right now.
>
> The following code is my simple idea, which might help you.
>
>
> #define MIGRATION_TYPE (MAX_SWAPFILES - 1)
>
> static inline int pte_is_migration(pte_t pte)
> {
> unsigned long swp_type;
> swp_entry_t arch_entry;
>
> arch_entry = __pte_to_swp_entry(pte);
>
> swp_type = __swp_type(arch_entry);
>
> return swp_type == MIGRATION_TYPE;
> }
OK thanks this code works fine (just pasted into swapops.h and tested).
Thanks.
> static inline int PageMigration(page)
> {
> swp_entry_t entry = { .val = page->private,};
> return (PageSwapCache(page) && swp_type(entry) == MIGRATION_TYPE);
> }
Oh and with that we no longer need PG_migration bit, but, page->private
does not contain swp_type information (MIGRATION_TYPE bit) in it. Its simply
an offset counting from 0 increasing sequentially.
ANDing migration type bit into the offset should work.
--
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>
next prev parent reply other threads:[~2004-10-23 19:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 19:22 [PATCH] Migration cache Marcelo Tosatti
2004-10-18 16:57 ` Hirokazu Takahashi
2004-10-20 17:10 ` Hirokazu Takahashi
2004-10-21 10:30 ` Marcelo Tosatti
2004-10-21 19:09 ` Hugh Dickins
2004-10-21 18:22 ` Marcelo Tosatti
2004-10-22 6:49 ` Hirokazu Takahashi
2004-10-23 19:28 ` Marcelo Tosatti [this message]
2004-10-23 22:26 ` Hugh Dickins
2004-10-24 12:21 ` Marcelo Tosatti
2004-10-24 15:37 ` Hugh Dickins
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=20041023192857.GA12334@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=haveblue@us.ibm.com \
--cc=hugh@veritas.com \
--cc=iwamoto@valinux.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=taka@valinux.co.jp \
/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.