[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dc2642fc-f662-41cd-a236-fccf4c252dfa@default>
Date: Sun, 7 Apr 2013 10:59:18 -0700 (PDT)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: Dan Magenheimer <dan.magenheimer@...cle.com>,
Wanpeng Li <liwanp@...ux.vnet.ibm.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Minchan Kim <minchan@...nel.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Fengguang Wu <fengguang.wu@...el.com>,
Bob Liu <bob.liu@...cle.com>, Ric Mason <ric.masonn@...il.com>
Subject: RE: [PATCH part2 v6 0/3] staging: zcache: Support zero-filled pages
more efficiently
> From: Dan Magenheimer
> Subject: RE: [PATCH part2 v6 0/3] staging: zcache: Support zero-filled pages more efficiently
>
> > From: Wanpeng Li [mailto:liwanp@...ux.vnet.ibm.com]
> > Subject: Re: [PATCH part2 v6 0/3] staging: zcache: Support zero-filled pages more efficiently
> >
> > Hi Dan,
> >
> > Some issues against Ramster:
> >
>
> Sure! I am concerned about Konrad's patches adding debug.c as they
> add many global variables. They are only required when ZCACHE_DEBUG
> is enabled so they may be ok. If not, adding ramster variables
> to debug.c may make the problem worse.
Oops, I just noticed/remembered that ramster uses BOTH debugfs and sysfs.
The sysfs variables are all currently required, i.e. for configuration
so should not be tied to debugfs or a DEBUG config option. However,
if there is a more acceptable way to implement the function of
those sysfs variables, that would be fine.
Thanks,
Dan
--
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