From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Dulloor <dulloor@gmail.com>, Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: tmem and construct_dom0 memory allocation race
Date: Tue, 22 Jun 2010 10:23:20 -0700 (PDT) [thread overview]
Message-ID: <2f4192b4-cdb8-495f-a469-b1dc2b4a9044@default> (raw)
In-Reply-To: <C84626FD.1827E%keir.fraser@eu.citrix.com>
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Subject: Re: [Xen-devel] tmem and construct_dom0 memory allocation race
>
> On 22/06/2010 08:17, "Dulloor" <dulloor@gmail.com> wrote:
>
> > Hi Keir, You are right .. there is no race. I spent some time
> > debugging this. The problem is that a zero-order allocation (from
> > alloc_chunk, for the last dom0 page) fails with tmem on (in
> > alloc_heap_pages), even though there are pages available in the heap.
> > I don't think tmem really intends to get triggered so early. What do
> > you think ?
>
> That's one for Dan to comment on.
Hmmm... the special casing in alloc_heap_pages to avoid fragmentation
need not be invoked if tmem doesn't hold any pages (as is the
case at dom0 boot)...
Does this patch fix the problem? If so...
Signed-off-by: Dan Magenheimer
diff -r a24dbfcbdf69 xen/common/page_alloc.c
--- a/xen/common/page_alloc.c Tue Jun 22 07:19:38 2010 +0100
+++ b/xen/common/page_alloc.c Tue Jun 22 11:17:44 2010 -0600
@@ -316,11 +316,14 @@ static struct page_info *alloc_heap_page
spin_lock(&heap_lock);
/*
- * TMEM: When available memory is scarce, allow only mid-size allocations
- * to avoid worst of fragmentation issues. Others try TMEM pools then fail.
+ * TMEM: When available memory is scarce due to tmem absorbing it, allow
+ * only mid-size allocations to avoid worst of fragmentation issues.
+ * Others try tmem pools then fail. This is a workaround until all
+ * post-dom0-creation-multi-page allocations can be eliminated.
*/
if ( opt_tmem && ((order == 0) || (order >= 9)) &&
- (total_avail_pages <= midsize_alloc_zone_pages) )
+ (total_avail_pages <= midsize_alloc_zone_pages) &&
+ tmem_freeable_pages() )
goto try_tmem;
/*
diff -r a24dbfcbdf69 xen/common/tmem.c
--- a/xen/common/tmem.c Tue Jun 22 07:19:38 2010 +0100
+++ b/xen/common/tmem.c Tue Jun 22 11:17:44 2010 -0600
@@ -2850,6 +2850,11 @@ EXPORT void *tmem_relinquish_pages(unsig
return pfp;
}
+EXPORT unsigned long tmem_freeable_pages(void)
+{
+ return tmh_freeable_pages();
+}
+
/* called at hypervisor startup */
static int __init init_tmem(void)
{
diff -r a24dbfcbdf69 xen/include/xen/tmem.h
--- a/xen/include/xen/tmem.h Tue Jun 22 07:19:38 2010 +0100
+++ b/xen/include/xen/tmem.h Tue Jun 22 11:17:44 2010 -0600
@@ -11,6 +11,7 @@
extern void tmem_destroy(void *);
extern void *tmem_relinquish_pages(unsigned int, unsigned int);
+extern unsigned long tmem_freeable_pages(void);
extern int opt_tmem;
#endif /* __XEN_TMEM_H__ */
next prev parent reply other threads:[~2010-06-22 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 23:10 tmem and construct_dom0 memory allocation race Dulloor
2010-06-19 7:26 ` Keir Fraser
2010-06-21 15:35 ` Dan Magenheimer
2010-06-22 7:17 ` Dulloor
2010-06-22 7:36 ` Jan Beulich
2010-06-22 7:38 ` Keir Fraser
2010-06-22 17:23 ` Dan Magenheimer [this message]
2010-06-22 18:56 ` Dulloor
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=2f4192b4-cdb8-495f-a469-b1dc2b4a9044@default \
--to=dan.magenheimer@oracle.com \
--cc=JBeulich@novell.com \
--cc=dulloor@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).