Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752847AbbBXV41 (ORCPT ); Tue, 24 Feb 2015 16:56:27 -0500 Received: from mail-ie0-f174.google.com ([209.85.223.174]:44330 "EHLO mail-ie0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752248AbbBXV40 (ORCPT ); Tue, 24 Feb 2015 16:56:26 -0500 MIME-Version: 1.0 In-Reply-To: <9cc2b63100622f5fd17fa5e4adc59233a2b41877.1424779443.git.aquini@redhat.com> References: <9cc2b63100622f5fd17fa5e4adc59233a2b41877.1424779443.git.aquini@redhat.com> Date: Tue, 24 Feb 2015 13:56:25 -0800 X-Google-Sender-Auth: wAtzRvC1YASr_euuKi0EWMZ1BtM Message-ID: Subject: Re: [PATCH] mm: readahead: get back a sensible upper limit From: Linus Torvalds To: Rafael Aquini Cc: linux-mm , Andrew Morton , Johannes Weiner , Rik van Riel , David Rientjes , Linux Kernel Mailing List , loberman@redhat.com, Larry Woodman , Raghavendra K T Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 765 Lines: 21 On Tue, Feb 24, 2015 at 4:58 AM, Rafael Aquini wrote: > > This patch brings back the old behavior of max_sane_readahead() Yeah no. There was a reason that code was killed. No way in hell are we bringing back the insanities with node memory etc. Also, we have never actually heard of anything sane that actualyl depended on this. Last time this came up it was a made-up benchmark, not an actual real load that cared. Who can possibly care about this in real life? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/