[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52E2A0C6.4030801@citrix.com>
Date: Fri, 24 Jan 2014 17:20:06 +0000
From: Zoltan Kiss <zoltan.kiss@...rix.com>
To: Matt Wilson <msw@...ux.com>
CC: <ian.campbell@...rix.com>, <wei.liu2@...rix.com>,
<xen-devel@...ts.xenproject.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <jonathan.davies@...rix.com>,
Anthony Liguori <aliguori@...zon.com>,
Matt Wilson <msw@...zon.com>
Subject: Re: [PATCH v6] xen/grant-table: Avoid m2p_override during mapping
On 24/01/14 05:48, Matt Wilson wrote:
> On Thu, Jan 23, 2014 at 09:23:44PM +0000, Zoltan Kiss wrote:
> Apologies for coming in late on this thread. I'm quite behind on
> xen-devel mail that isn't CC: to me.
>
> It seems to have been forgotten that Anthony and I proposed a similar
> change last November.
>
> https://lkml.kernel.org/r/1384307336-5328-1-git-send-email-anthony@codemonkey.ws
>
> Or am I misunderstanding the change?
I didn't know about this patch, but yes, both of them do basically the
same. One subtle difference that you store the old mfn in page->private,
while my patch keeps the original behaviour, and store it in
page->index. page->private is used instead to store the new mfn we got
from Xen, however I haven't checked where do we use that.
Your approach might be better, we also talked with David that we should
stop using page->index, as e.g. with the netback grant mapping patches I
spent a lot of time to figure out a packet drop issue, which eventually
boiled down to the fact that index is in union with pfmemalloc, and if
you don't set mapping, the local IP stack will think it is a pfmemalloc
page. (see the comment in my second patch, xenvif_fill_frags)
However I think that should be a separate patch, I tried to keep the
original behaviour as much as possible, and focus just on avoiding
m2p_override when possible.
Regards,
Zoli
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists