linux-kernel - Re: [PATCH 0/5] WorkStruct: Shrink work

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]

Date:	Thu, 23 Nov 2006 17:01:22 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	David Howells <dhowells@...hat.com>
CC:	Andrew Morton <akpm@...l.org>, torvalds@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] WorkStruct: Shrink work_struct by two thirds

David Howells wrote:
> Andrew Morton <akpm@...l.org> wrote:
>> waaaaaaaay too many rejects for me, sorry.
...
> Actually... there is a way to do this sort of incrementally,
...
> Might that help?

I'd say, do it one step, as quickly as you can. And do it on top of
-rc1. For now you could test for yourself to rebase your current
patchset onto -mm --- just to get an impression of the steps you will
have to go through once you have an -rc1 to work with.

Maybe it's a bit less trouble if you split the patchset per subsystem,
in a similar manner as the various patch collections in -mm are divided
per subsystem or subproject. This would also allow you to reuse parts of
an -mm rebase from now for a -rc1 rebase later. I.e. go for more
parallelism, not for more sequential steps. (...am I naively suggesting,
without any own experience in such things.)
-- 
Stefan Richter
-=====-=-==- =-== =-===
http://arcgraph.de/sr/
-
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/