[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTil9hGHoomM9LlhURipKO7_sTON09JHP3zDwOLgI@mail.gmail.com>
Date: Tue, 13 Jul 2010 20:53:43 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Xiaotian Feng <dfeng@...hat.com>
Cc: linux-mm@...ck.org, linux-nfs@...r.kernel.org,
netdev@...r.kernel.org, riel@...hat.com, cl@...ux-foundation.org,
a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org,
lwang@...hat.com, penberg@...helsinki.fi,
akpm@...ux-foundation.org, davem@...emloft.net
Subject: Re: [PATCH -mmotm 00/30] [RFC] swap over nfs -v21
On Tue, Jul 13, 2010 at 6:16 PM, Xiaotian Feng <dfeng@...hat.com> wrote:
> Hi,
>
> Here's the latest version of swap over NFS series since -v20 last October. We decide to push
> this feature as it is useful for NAS or virt environment.
>
> The patches are against the mmotm-2010-07-01. We can split the patchset into following parts:
>
> Patch 1 - 12: provides a generic reserve framework. This framework
> could also be used to get rid of some of the __GFP_NOFAIL users.
>
> Patch 13 - 15: Provide some generic network infrastructure needed later on.
>
> Patch 16 - 21: reserve a little pool to act as a receive buffer, this allows us to
> inspect packets before tossing them.
>
> Patch 22 - 23: Generic vm infrastructure to handle swapping to a filesystem instead of a block
> device.
>
> Patch 24 - 27: convert NFS to make use of the new network and vm infrastructure to
> provide swap over NFS.
>
> Patch 28 - 30: minor bug fixing with latest -mmotm.
>
> [some history]
> v19: http://lwn.net/Articles/301915/
> v20: http://lwn.net/Articles/355350/
>
> Changes since v20:
> - rebased to mmotm-2010-07-01
> - dropped the null pointer deref patch for the root cause is wrong SWP_FILE enum
> - some minor build fixes
> - fix a null pointer deref with mmotm-2010-07-01
> - fix a bug when swap with multi files on the same nfs server
Please use the "From:" line correctly, as stated in
Documentation/SubmittingPatches:
The "from" line must be the very first line in the message body,
and has the form:
From: Original Author <author@...mple.com>
The "from" line specifies who will be credited as the author of the
patch in the permanent changelog. If the "from" line is missing,
then the "From:" line from the email header will be used to determine
the patch author in the changelog.
I think you are using git format-patch to generate those patches, please supply
--author=<author> to git commit when you commit them to your local
tree. (or git am
if the patches you received already had the correct From: line.)
Thanks.
--
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