From: Hollis Blanchard <hollisb@us.ibm.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: xen-ia64-devel@lists.xensource.com,
xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>,
xen-ppc-devel@lists.xensource.com
Subject: Re: Re: [Xen-devel] [PATCH] [GNTTAB] expandable grant table
Date: Mon, 26 Feb 2007 17:31:08 -0600 [thread overview]
Message-ID: <1172532668.910.34.camel@basalt> (raw)
In-Reply-To: <20070219080312.GB10839%yamahata@valinux.co.jp>
On Mon, 2007-02-19 at 17:03 +0900, Isaku Yamahata wrote:
> Attached the updated patches. Please find them
>
> - 13985_4fa9b86d41b8_grow_granttable_acm.patch
> acm part. I did only compile test.
>
> - 13986_cca098fd122c_grow_granttable_ia64.patch
> ia64 part.
>
> - 13987_f5f232aef7bd_grow_granttable_powerpc.patch
> powerpc part. This patch prohibits growing grant table.
> I didn't even compile test.
> It needs review by xen/powerpc developers and they may
> have their own opinions.
Hi Yamahata-san, thanks very much for your patch!
I'm confused about one thing though: why do we need to take a lock to
read d->grant_table->nr_grant_frames? It's a simple integer, so no lock
is required or useful.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2007-02-26 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eab087540611141441s4fbe89b8k48e062c51730932a@mail.gmail.com>
2007-01-05 13:43 ` [PATCH] [GNTTAB] expandable grant table Keir Fraser
2007-01-06 6:48 ` Isaku Yamahata
2007-02-15 14:39 ` Keir Fraser
2007-02-15 15:38 ` Isaku Yamahata
2007-02-19 8:03 ` Isaku Yamahata
2007-02-26 23:31 ` Hollis Blanchard [this message]
2007-02-26 23:39 ` [XenPPC] Re: [Xen-devel] " Keir Fraser
2007-02-27 0:05 ` [XenPPC] " Hollis Blanchard
2007-02-27 7:50 ` [XenPPC] Re: [Xen-devel] " Keir Fraser
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=1172532668.910.34.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
--cc=xen-ppc-devel@lists.xensource.com \
--cc=yamahata@valinux.co.jp \
/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.