From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: linux-mm@kvack.org, iwamoto@valinux.co.jp, haveblue@us.ibm.com,
hugh@veritas.com
Subject: Re: migration cache, updated
Date: Tue, 26 Oct 2004 09:41:16 -0200 [thread overview]
Message-ID: <20041026114116.GB27014@logos.cnet> (raw)
In-Reply-To: <20041026.224550.109999656.taka@valinux.co.jp>
On Tue, Oct 26, 2004 at 10:45:50PM +0900, Hirokazu Takahashi wrote:
> Hi,
>
> > > The previous code will cause deadlock, as the page is already locked.
> >
> > Actually this one is fine - the page is not locked (its locked
> > by the SwapCache pte path - not migration path)
> >
> > if (pte_is_migration(pte))
> > lookup_migration_cache
> > else
> > old lookup swap cache
> > lock_page
> >
> > if (pte_is_migration(pte))
> > mark_page_accessed
> > lock_page
>
> Oh, I understand.
>
> > Can you please try the tests with the following updated patch
> >
> > Works for me
>
> It didn't work without one fix.
>
> +void remove_from_migration_cache(struct page *page, int id)
> +{
> + write_lock_irq(&migration_space.tree_lock);
> + idr_remove(&migration_idr, id);
> + radix_tree_delete(&migration_space.page_tree, id);
> + ClearPageSwapCache(page);
> + page->private = NULL;
> + write_unlock_irq(&migration_space.tree_lock);
> +}
>
> +int migration_remove_reference(struct page *page)
> +{
> + struct counter *c;
> + swp_entry_t entry;
> +
> + entry.val = page->private;
> +
> + read_lock_irq(&migration_space.tree_lock);
> +
> + c = idr_find(&migration_idr, swp_offset(entry));
> +
> + read_unlock_irq(&migration_space.tree_lock);
> +
> + if (!c->i)
> + BUG();
> +
> + c->i--;
> +
> + if (!c->i) {
> + remove_from_migration_cache(page, page->private);
> + kfree(c);
>
> page_cache_release(page) should be invoked here, as the count for
> the migration cache must be decreased.
> With this fix, your migration cache started to work very fine!
Oh yes, I removed that by accident.
> + }
> +
> +}
>
>
>
> The attached patch is what I ported your patch to the latest version
> and I fixed the bug.
It seems a hunk from your own tree leaked into this patch?
See above
> @@ -367,11 +527,6 @@ generic_migrate_page(struct page *page,
>
> /* map the newpage where the old page have been mapped. */
> touch_unmapped_address(&vlist);
> - if (PageSwapCache(newpage)) {
> - lock_page(newpage);
> - __remove_exclusive_swap_page(newpage, 1);
> - unlock_page(newpage);
> - }
>
> page->mapping = NULL;
> unlock_page(page);
> @@ -383,11 +538,6 @@ out_busy:
> /* Roll back all operations. */
> rewind_page(page, newpage);
> touch_unmapped_address(&vlist);
> - if (PageSwapCache(page)) {
> - lock_page(page);
> - __remove_exclusive_swap_page(page, 1);
> - unlock_page(page);
> - }
> return ret;
This two hunks?
OK fine I'll update the patch with all fixes to
the newer version of -mhp, and start working
on the nonblocking version of the migration
functions.
--
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-26 11:41 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 21:39 Marcelo Tosatti
2004-10-26 1:17 ` Hiroyuki KAMEZAWA
2004-10-26 12:01 ` Marcelo Tosatti
2004-10-26 23:47 ` Hiroyuki KAMEZAWA
2004-10-26 6:37 ` Hirokazu Takahashi
2004-10-26 9:20 ` Marcelo Tosatti
2004-10-26 13:45 ` Hirokazu Takahashi
2004-10-26 11:41 ` Marcelo Tosatti [this message]
2004-10-27 13:40 ` Hirokazu Takahashi
2004-10-26 9:15 ` Hirokazu Takahashi
2004-10-26 9:25 ` Marcelo Tosatti
2004-10-26 14:01 ` Hirokazu Takahashi
2004-10-26 12:24 ` Marcelo Tosatti
2004-10-27 7:25 ` IWAMOTO Toshihiro
2004-10-27 16:27 ` Marcelo Tosatti
2004-10-27 13:48 ` Hirokazu Takahashi
2004-10-28 15:19 ` Marcelo Tosatti
2004-10-28 16:05 ` Marcelo Tosatti
2004-10-28 18:51 ` Dave Hansen
2004-10-28 16:26 ` Marcelo Tosatti
2004-10-28 20:24 ` Dave Hansen
2004-11-03 15:21 ` Marcelo Tosatti
2004-11-04 8:01 ` Hirokazu Takahashi
2004-11-05 13:49 ` Hirokazu Takahashi
2004-11-05 15:16 ` Marcelo Tosatti
2004-11-16 4:07 ` Hirokazu Takahashi
2004-11-23 12:14 ` Marcelo Tosatti
2004-11-24 10:21 ` Hirokazu Takahashi
2004-12-01 20:21 ` Marcelo Tosatti
2004-12-08 13:23 ` Hirokazu Takahashi
2005-01-17 9:59 ` Marcelo Tosatti
2005-01-31 18:33 ` Ray Bryant
2005-01-31 18:44 ` Marcelo Tosatti
2005-02-02 21:28 ` Ray Bryant
2005-02-03 2:59 ` Hirokazu Takahashi
2005-02-03 15:19 ` Ray Bryant
2005-02-04 7:32 ` Hirokazu Takahashi
2005-02-04 16:08 ` Ray Bryant
2005-02-07 12:46 ` Hirokazu Takahashi
2005-02-07 20:54 ` Ray Bryant
2005-02-08 2:17 ` Hirokazu Takahashi
[not found] ` <42083913.9050306@sgi.com>
[not found] ` <20050209.151938.63052333.taka@valinux.co.jp>
2005-02-09 20:48 ` Ray Bryant
2005-02-07 13:16 ` Hirokazu Takahashi
2005-02-03 2:49 ` Hirokazu Takahashi
2005-01-03 19:04 page migration Ray Bryant
2005-01-03 19:37 ` Dave Hansen
2005-01-03 20:15 ` Ray Bryant
2005-01-04 14:42 ` Hirokazu Takahashi
2005-01-04 17:30 ` Ray Bryant
2005-01-04 17:40 ` process " Dave Hansen
2005-01-04 18:26 ` Ray Bryant
2005-01-07 16:57 ` migration cache, updated Ray Bryant
2005-01-10 10:07 ` Marcelo Tosatti
2005-01-03 19:25 Ray Bryant
2005-02-06 2:02 Marcelo Tosatti
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=20041026114116.GB27014@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=haveblue@us.ibm.com \
--cc=hugh@veritas.com \
--cc=iwamoto@valinux.co.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox