From: "Andres Lagar-Cavilla" <andres@lagarcavilla.org>
To: Tim Deegan <tim@xen.org>
Cc: adin@gridcentric.ca, andres@gridcentric.ca, keir.xen@gmail.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH 2 of 3] x86/mem_sharing: modularize reverse map for shared frames
Date: Wed, 18 Apr 2012 07:19:57 -0700 [thread overview]
Message-ID: <f73ef505cf67b715cbf37b6f63a4db3e.squirrel@webmail.lagarcavilla.org> (raw)
In-Reply-To: <20120418140550.GH7013@ocelot.phlegethon.org>
> At 10:16 -0400 on 12 Apr (1334225773), Andres Lagar-Cavilla wrote:
>> /* Do the accounting first. If anything fails below, we have bigger
>> * bigger fish to fry. First, remove the gfn from the list. */
>> - last_gfn = list_has_one_entry(&page->sharing->gfns);
>> + last_gfn = rmap_has_one_entry(page);
>> if ( last_gfn )
>> {
>> - /* Clean up shared state */
>> - audit_del_list(page);
>> + /* Clean up shared state. Get rid of the <domid, gfn> tuple
>> + * before destroying the rmap. */
>> + mem_sharing_gfn_destroy(page, d, gfn_info);
>
> Moving this mem_sharing_gfn_destroy() around seems like it's unrelated
> to the rest of this patch, which is basically code motion. If so, can
> you put it in a patch of its own?
Sure. I'll split it up but wait for feedback on 3.3 before re-submit.
Andres
>
> Otherwise, pending patch 3/3 being OK too,
>
> Acked-by: Tim Deegan <tim@xen.org>
>
>> + page_sharing_dispose(page);
>> page->sharing = NULL;
>> atomic_dec(&nr_shared_mfns);
>> }
>> else
>> atomic_dec(&nr_saved_mfns);
>> +
>> /* If the GFN is getting destroyed drop the references to MFN
>> * (possibly freeing the page), and exit early */
>> if ( flags & MEM_SHARING_DESTROY_GFN )
>> {
>> - mem_sharing_gfn_destroy(d, gfn_info);
>> + if ( !last_gfn )
>> + mem_sharing_gfn_destroy(page, d, gfn_info);
>> put_page_and_type(page);
>> mem_sharing_page_unlock(page);
>> if ( last_gfn &&
>> @@ -987,7 +1052,6 @@ gfn_found:
>>
>> if ( last_gfn )
>> {
>> - mem_sharing_gfn_destroy(d, gfn_info);
>> /* Making a page private atomically unlocks it */
>> BUG_ON(page_make_private(d, page) != 0);
>> goto private_page_found;
>> @@ -1011,7 +1075,7 @@ gfn_found:
>> unmap_domain_page(t);
>>
>> BUG_ON(set_shared_p2m_entry(d, gfn, page_to_mfn(page)) == 0);
>> - mem_sharing_gfn_destroy(d, gfn_info);
>> + mem_sharing_gfn_destroy(old_page, d, gfn_info);
>> mem_sharing_page_unlock(old_page);
>> put_page_and_type(old_page);
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2012-04-18 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 14:16 [PATCH 0 of 3] RFC: x86 memory sharing performance improvements Andres Lagar-Cavilla
2012-04-12 14:16 ` [PATCH 1 of 3] x86/mm/sharing: Clean ups for relinquishing shared pages on destroy Andres Lagar-Cavilla
2012-04-18 12:42 ` Tim Deegan
2012-04-18 13:06 ` Andres Lagar-Cavilla
2012-04-12 14:16 ` [PATCH 2 of 3] x86/mem_sharing: modularize reverse map for shared frames Andres Lagar-Cavilla
2012-04-18 14:05 ` Tim Deegan
2012-04-18 14:19 ` Andres Lagar-Cavilla [this message]
2012-04-12 14:16 ` [PATCH 3 of 3] x86/mem_sharing: For shared pages with many references, use a hash table instead of a list Andres Lagar-Cavilla
2012-04-18 15:35 ` Tim Deegan
2012-04-18 16:18 ` Andres Lagar-Cavilla
2012-04-24 19:33 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2012-04-24 19:48 [PATCH 0 of 3] x86/mem_sharing: Improve performance of rmap, fix cascading bugs Andres Lagar-Cavilla
2012-04-24 19:48 ` [PATCH 2 of 3] x86/mem_sharing: modularize reverse map for shared frames Andres Lagar-Cavilla
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=f73ef505cf67b715cbf37b6f63a4db3e.squirrel@webmail.lagarcavilla.org \
--to=andres@lagarcavilla.org \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).