linux-kernel - Re: [PATCH 00/21] mm: Preemptibility -v6

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: <1295346647.30950.477.camel@laptop>
Date:	Tue, 18 Jan 2011 11:30:47 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Hugh Dickins <hughd@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	David Miller <davem@...emloft.net>,
	Nick Piggin <npiggin@...nel.dk>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	linux-mm@...ck.org
Subject: Re: [PATCH 00/21] mm: Preemptibility -v6

On Mon, 2011-01-17 at 23:12 -0800, Hugh Dickins wrote:
> I understand you're intending to update your preemptible mmu_gather
> patchset against 2.6.38-rc1, so I've spent a while looking through
> (and running) your last posted version (plus its two fixes from BenH).
> 
> I've had no problems in running it, I can't tell if it's quicker or
> slower than the unpatched.  The only argument against the patchset,
> really, would be performance: and though there are no bad reports on
> it as yet, I do wonder how we proceed if a genuine workload shows up
> which is adversely affected.  Oh well, silly to worry about the
> hypothetical I suppose.
> 
Wow, _HUGE_ review, thanks! I'll slowly make my way through it when I do
the rebase against .38-rc1, most suggestions look very good indeed.

And as to performance, there's the no-regression report from Yanmin
running it through the Intel test farm. However Nick also had a
particular workload he wanted to test, Nick, do you think you've got a
few spare minutes to dig that workload up and give it a run?

But I guess you're right, there's always a chance someone hits
something, and I guess there's nothing to it but to deal with it when
that comes..
--
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/