linux-kernel - Re: [RFC][PATCH] Remove cgroup member from struct page

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200809011743.42658.nickpiggin@yahoo.com.au>
Date:	Mon, 1 Sep 2008 17:43:42 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	balbir@...ux.vnet.ibm.com,
	Andrew Morton <akpm@...ux-foundation.org>, hugh@...itas.com,
	menage@...gle.com, xemul@...nvz.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [RFC][PATCH] Remove cgroup member from struct page

On Monday 01 September 2008 17:19, KAMEZAWA Hiroyuki wrote:
> On Mon, 1 Sep 2008 16:56:44 +1000
>
> Nick Piggin <nickpiggin@...oo.com.au> wrote:
> > On Monday 01 September 2008 10:01, KAMEZAWA Hiroyuki wrote:
> > > On Sun, 31 Aug 2008 23:17:56 +0530
> > >
> > > Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
> > > > This is a rewrite of a patch I had written long back to remove struct
> > > > page (I shared the patches with Kamezawa, but never posted them
> > > > anywhere else). I spent the weekend, cleaning them up for
> > > > 2.6.27-rc5-mmotm (29 Aug 2008).
> > >
> > > It's just because I think there is no strong requirements for 64bit
> > > count/mapcount. There is no ZERO_PAGE() for ANON (by Nick Piggin. I add
> > > him to CC.) (shmem still use it but impact is not big.)
> >
> > I think it would be nice to reduce the impact when it is not configured
> > anyway. Normally I would not mind so much, but this is something that
> > many distros will want to enable but fewer users will make use of it.
> >
> > I think it is always a very good idea to try to reduce struct page size.
> > When looking at the performance impact though, just be careful with the
> > alignment of struct page... I actually think it is going to be a
> > performance win in many cases to make struct page 64 bytes.
>
> On 32bit, sizeof(struct page) = 32bytes + 4bytes(page_cgroup)
> On 64bit, sizeof(struct page) = 56bytes + 8bytes(page_cgroup)
> So, 32bit case is a problem.

Right. Well, either one is a problem because we always prefer to have
less things in struct page rather than more ;)


> > If you do that, it might even be an idea to allocate flat arrays with
> > bootmem. It would just be slightly more tricky more tricky to fit this
> > in with the memory model. But that's not a requirement, just an idea
> > for a small optimisation.
>
> If we make mem_res_controller available only under SPARSEMEM, I think we
> can do in very straightfoward way.

That could be a reasonable solution.  Balbir has other concerns about
this... so I think it is OK to try the radix tree approach first.
--
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/