linux-kernel - Re: [PATCH 0/13] maps: pagemap, kpagemap, and related cleanups

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:	Fri, 13 Apr 2007 17:05:47 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	William Lee Irwin III <wli@...omorphy.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Matt Mackall <mpm@...enic.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/13] maps: pagemap, kpagemap, and related cleanups

William Lee Irwin III wrote:
> Andrew Morton wrote:
> 
>>>Then you just end up with the same thing, don't you?
> 
> 
> On Fri, Apr 13, 2007 at 12:50:20PM +1000, Nick Piggin wrote:
> 
>>Well _you_ do, because that happens to be exactly what you want. Bill
>>ends up with something that displays page_mapcount instead. And I
>>end up with something that traverses LRU lists rather than pfns. And
>>none of it goes in /proc/ or linux-2.6/.
>>So it isn't really the same thing at all.
> 
> 
> The EM guys aren't dealing with the database; they're dealing with some
> enterprise management thingie that does things like control how many
> client connections are allowed for each database instance. Unless
> they're doing less than I expect, and are largely something like procps
> on steroids and enterprise silliness.

Ah, OK. Anyway, with kprobes/systemtap they can do whatever they like
and none of us need to care in the slightest ;)

-- 
SUSE Labs, Novell Inc.
-
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/