From: Hongkaixing <hongkaixing@huawei.com>
To: 'Olaf Hering' <olaf@aepfle.de>
Cc: bicky.shi@huawei.com, xiaowei.yang@huawei.com,
xen-devel@lists.xensource.com, yanqiangjun@huawei.com,
hanweidong@huawei.com
Subject: Re: [PATCH] xenpaging:add a new array to speed up page-in in xenpaging
Date: Sat, 07 Jan 2012 16:55:49 +0800 [thread overview]
Message-ID: <002c01cccd1a$279c9a00$76d5ce00$@com> (raw)
In-Reply-To: <20120106130737.GB1694@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Friday, January 06, 2012 9:08 PM
> To: hongkaixing@huawei.com
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [PATCH] xenpaging:add a new array to speed up page-in in xenpaging
>
> On Thu, Jan 05, Olaf Hering wrote:
>
> > Is the page-out time for 512M really that fast? For me page-out is still
> > really slow even when the pagefile is in tmpfs. It takes several
> > minutes, I get around 4MB/s. page-in is around 20MB/s.
>
> Wait, the slow page-out is due to the poll() timeout in
> xenpaging_wait_for_event_or_timeout(). This can be fixed with some sort
> of dynamic timeout while there is still something to page-out.
I don't think so. Our approach still use 100ms in poll(), Using 10ms seems no significant change.
In my opinion, In order to improve speed , 2 points are necessary:
1. put page-in request fast
2. request should be in disk order. Especially for a large swap file.
>
> Olaf
next prev parent reply other threads:[~2012-01-07 8:55 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
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 [this message]
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='002c01cccd1a$279c9a00$76d5ce00$@com' \
--to=hongkaixing@huawei.com \
--cc=bicky.shi@huawei.com \
--cc=hanweidong@huawei.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xensource.com \
--cc=xiaowei.yang@huawei.com \
--cc=yanqiangjun@huawei.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).