From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Steven Smith <steven.smith@citrix.com>
Subject: Re: [Pv-ops][PATCH 2/4 v2] Netback: Introduce a new struct type page_ext.
Date: Mon, 3 May 2010 12:05:40 -0400 [thread overview]
Message-ID: <20100503160540.GD31299@phenom.dumpdata.com> (raw)
In-Reply-To: <D5AB6E638E5A3E4B8F4406B113A5A19A1D94B189@shsmsx501.ccr.corp.intel.com>
On Thu, Apr 29, 2010 at 10:28:36PM +0800, Xu, Dongxiao wrote:
> Netback: Introduce a new struct type page_ext.
>
> struct page_ext is used to store the group and idx information by
> which a specified page could be identified.
>
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
.. snip..
-static inline int netif_page_index(struct page *pg)
-{
- unsigned long idx = (unsigned long)pg->mapping - 1;
-
- if (!PageForeign(pg))
- return -1;
You are taking the check to see if the page is foreign. Is that OK?
-
- if ((idx >= MAX_PENDING_REQS) || (netbk->mmap_pages[idx] != pg))
- return -1;
-
- return idx;
+ pg->mapping = (struct address_space *)page_extinfo;;
}
/*
@@ -1411,9 +1399,10 @@ static void netif_idx_release(u16 pending_idx)
static void netif_page_release(struct page *page, unsigned int order)
{
- int idx = netif_page_index(page);
This did this nice little check to see if the page had the PageForeign
bit set. Is it OK to remove that check?
- BUG_ON(order);
- BUG_ON(idx < 0);
+ int idx = ((struct page_ext *)(page->mapping))->idx;
+ BUG_ON(order ||
+ idx < 0 || idx >= MAX_PENDING_REQS ||
+ netbk->mmap_pages[idx] != page);
netif_idx_release(idx);
}
@@ -1565,7 +1554,9 @@ static int __init netback_init(void)
for (i = 0; i < MAX_PENDING_REQS; i++) {
page = netbk->mmap_pages[i];
SetPageForeign(page, netif_page_release);
- netif_set_page_index(page, i);
+ netbk->page_extinfo[i].group = 0;
+ netbk->page_extinfo[i].idx = i;
+ netif_set_page_index(page, &netbk->page_extinfo[i]);
INIT_LIST_HEAD(&netbk->pending_inuse[i].list);
}
--
1.6.0
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-03 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 14:28 [Pv-ops][PATCH 2/4 v2] Netback: Introduce a new struct type page_ext Xu, Dongxiao
2010-05-03 16:05 ` Konrad Rzeszutek Wilk [this message]
2010-05-04 0:51 ` Xu, Dongxiao
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=20100503160540.GD31299@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dongxiao.xu@intel.com \
--cc=jeremy@goop.org \
--cc=steven.smith@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 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.