From: Hongkaixing <hongkaixing@huawei.com>
To: 'Ian Jackson' <Ian.Jackson@eu.citrix.com>
Cc: "'bicky.'" <bicky.shi@huawei.com>, 'Olaf Hering' <olaf@aepfle.de>,
xen-devel@lists.xensource.com
Subject: Re: [PATCH] xenpaging:add a new array to speed up page-in in xenpaging
Date: Fri, 06 Jan 2012 10:35:12 +0800 [thread overview]
Message-ID: <001301cccc1b$d7ca1470$875e3d50$@com> (raw)
In-Reply-To: <20229.60517.106414.825193@mariner.uk.xensource.com>
> -----邮件原件-----
> 发件人: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> 发送时间: 2012年1月6日 2:31
> 收件人: hongkaixing@huawei.com
> 抄送: Olaf Hering; xen-devel@lists.xensource.com
> 主题: Re: [Xen-devel] [PATCH] xenpaging:add a new array to speed up
page-in
> in xenpaging
>
> hongkaixing@huawei.com writes ("[Xen-devel] [PATCH] xenpaging:add a new
> array to speed up page-in in xenpaging"):
> > xenpaging:add a new array to speed up page-in in xenpaging
>
> Oh, and a couple of style points. You should keep to the style of the
> code you're editing. So:
>
> > + if (NULL == victims)
>
> In the xenpaging code this is written like this:
>
> if (victims == NULL)
>
Oh, This is our coding style, I will modify it according your opinion.
> You should do the same, throughout.
>
> > + page_out_index = (victim_to_i_t
> *)calloc(paging->domain_info->max_pages, sizeof(victim_to_i_t));
>
> Do not cast the return value from malloc et al.
>
> > + i = page_out_index[req.gfn].index ;
>
> The space before the semicolon is not the conventional style.
>
> > + if( victims[i].gfn !=INVALID_MFN )
>
> > - free(victims);
> > + if ( NULL != victims )
> > + {
> > + free(victims);
> > + }
>
> This is simply pointless. free(NULL) is legal.
I see...
>
> > +typedef struct victim_to_i {
> > + /* the index of victim array to read from */
> > + int index;
> > +} victim_to_i_t;
>
> 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;
>
> Use of types with names ending in _t is reserved to the C
> implementation (compiler and runtime). I know xenpaging is full of
> these but we shouldn't introduce any more.
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-06 2:35 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 [this message]
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
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='001301cccc1b$d7ca1470$875e3d50$@com' \
--to=hongkaixing@huawei.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=bicky.shi@huawei.com \
--cc=olaf@aepfle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.