linux-kernel - Re: [PATCH 2/2][-mm][resend] memcg limit change shrink usage.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080728015313.b4628537.akpm@linux-foundation.org>
Date:	Mon, 28 Jul 2008 01:53:13 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	kamezawa.hiroyu@...fujitsu.com
Cc:	linux-mm@...ck.org, balbir@...ux.vnet.ibm.com, xemul@...nvz.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2][-mm][resend] memcg limit change shrink usage.

On Mon, 28 Jul 2008 17:43:22 +0900 (JST) kamezawa.hiroyu@...fujitsu.com wrote:

> >Guys, this is core Linux kernel, not some weekend hack project.  Please
> >work to make it as comprehensible and as maintainable as we possibly
> >can.
> >
> >Also, it is frequently a mistake for a callee to assume that the caller
> >can use GFP_KERNEL.  Often when we do this we end having to change the
> >interface so that the caller passes in the gfp_t.  As there's only one
> >caller I guess we can get away with it this time.  For now.
> >
> 
> Hmm, ok. will rework this and take gfp_t as an argument.

I don't think it's necessary, really.  I was just talking to myself ;)
--
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/