xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Hongkaixing <hongkaixing@huawei.com>
Cc: "'bicky.'" <bicky.shi@huawei.com>,
	xen-devel@lists.xensource.com,
	'Ian Jackson' <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] xenpaging:add a new array to speed up page-in in xenpaging
Date: Tue, 10 Jan 2012 18:39:57 +0100	[thread overview]
Message-ID: <20120110173956.GA2213@aepfle.de> (raw)
In-Reply-To: <001301cccc1b$d7ca1470$875e3d50$@com>

On Fri, Jan 06, Hongkaixing wrote:

> > Why wrap this up in a struct ?
> 
> We want to keep the same style with
> 
> typedef struct xenpaging_victim {
>     /* the gfn of the page to evict */
>     unsigned long gfn;
> } xenpaging_victim_t;

This dates back to the initial implementation of xenpaging.

In my testing I started a guest paused, paged it all out, and paged all
back into memory. By monitoring nr_pages I noticed that page-in got
slightly slower over time, so your suggestion to use two indexes will
speed things up a bit.


Looking through xenpaging.c, I think its best to have two flat arrays:
unsigned long slot_to_gfn[paging->max_pages]; /* was victims */
int gfn_to_slot[paging->max_pages];

I will prepare a patch to implement this.

Olaf

  reply	other threads:[~2012-01-10 17:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05  3:08 [PATCH] xenpaging:add a new array to speed up page-in in xenpaging hongkaixing
2012-01-05 18:27 ` Ian Jackson
2012-01-06  2:35   ` Hongkaixing
2012-01-05 18:31 ` Ian Jackson
2012-01-06  2:35   ` Hongkaixing
2012-01-10 17:39     ` Olaf Hering [this message]
2012-01-11  7:15       ` Hongkaixing
2012-01-12 14:20         ` Olaf Hering
2012-01-09 11:50   ` Olaf Hering
2012-01-05 20:59 ` Olaf Hering
2012-01-06  2:35   ` Hongkaixing
2012-01-06 13:07   ` Olaf Hering
2012-01-07  8:55     ` Hongkaixing
2012-01-09 13:13       ` Olaf Hering

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=20120110173956.GA2213@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=bicky.shi@huawei.com \
    --cc=hongkaixing@huawei.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).