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: <200702100750.22487.kernel@kolivas.org>
Date:	Sat, 10 Feb 2007 07:50:22 +1100
From:	Con Kolivas <kernel@...ivas.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	jos poortvliet <jos@...nkamer.nl>, ck@....kolivas.org,
	linux-kernel@...r.kernel.org
Subject: Re: [ck] Re: Swap prefetch merge plans

On Saturday 10 February 2007 07:30, Andrew Morton wrote:
> On Fri, 09 Feb 2007 14:13:03 +0100
>
> jos poortvliet <jos@...nkamer.nl> wrote:
> > Nick's comment, replying to me some time ago:
>
> I think I was thinking of this:
>
> 	http://lkml.org/lkml/2006/2/6/509

Fortunately that predates a lot of changes where I did address all those. 
These will seem out of context without looking at that original email so I 
apologise in advance.

buffered_rmqueue and prefetching x86 specific (not into DMA) were dropped

It is NUMA aware

Global cacheline bouncing in page allocation and page reclaim paths I have no 
answer for as I have to tell swap prefetch that the vm is busy somehow and I 
do that by setting precisely one bit in a lockless manner.

The trylocks were dropped.

The other ideas were to :
-extend the prefetching. That's extra features
-knowing for sure when a system is really idle. I've tried hard to do that as 
cheaply as possible.
-putting pages on the lru? well it puts them on the tail
-papering over an issue? As I said, no matter how good the vm is, there will 
always be loads that swap.

-- 
-ck
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ