From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx149.postini.com [74.125.245.149]) by kanga.kvack.org (Postfix) with SMTP id 0C5356B0005 for ; Wed, 20 Mar 2013 16:58:59 -0400 (EDT) Date: Wed, 20 Mar 2013 13:58:58 -0700 From: Andrew Morton Subject: Re: [patch 1/4 v3]swap: change block allocation algorithm for SSD Message-Id: <20130320135858.179ceef83b43ce434373d55b@linux-foundation.org> In-Reply-To: References: <20130221021710.GA32580@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Hugh Dickins Cc: Shaohua Li , Rafael Aquini , riel@redhat.com, minchan@kernel.org, kmpark@infradead.org, linux-mm@kvack.org On Tue, 19 Mar 2013 13:50:57 -0700 (PDT) Hugh Dickins wrote: > I find it a bit confusing that we now have these two different clustering > strategies in scan_swap_map(), one for SSD and one for the rest; and it's > not immediately obvious what's used for what. Yes, having two separation allocation paths is bad and we should work to avoid it, please. Sooner rather than later (which sometimes never comes). We have a few theories about how the SSD code will worsen things for rotating disks. But have those theories been tested? Any performance results? If regressions *are* observed, what is the feasibility of fixing them up? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org