Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755859Ab2KHOAa (ORCPT ); Thu, 8 Nov 2012 09:00:30 -0500 Received: from mail-ee0-f46.google.com ([74.125.83.46]:61550 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751304Ab2KHOA2 convert rfc822-to-8bit (ORCPT ); Thu, 8 Nov 2012 09:00:28 -0500 MIME-Version: 1.0 In-Reply-To: <509BB4FE.60903@odi.ch> References: <509BA0F9.304@odi.ch> <509BB4FE.60903@odi.ch> Date: Thu, 8 Nov 2012 09:00:27 -0500 Message-ID: Subject: Re: [headache] 3.7.0-rc2 can't handle mutt (with 3.7G mail file) +FF (4 tabs) on a 4G memory+4 core system ? From: Luming Yu To: =?UTF-8?Q?Ortwin_Gl=C3=BCck?= Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 870 Lines: 24 On Thu, Nov 8, 2012 at 8:34 AM, Ortwin Glück wrote: > > > On 08.11.2012 14:28, Luming Yu wrote: >> >> As I just noticed that I couldn't quit from mutt due to tmpfs is full. > > > That's also pointing towards high memory pressure. watch "cat /proc/meminfo" just showed me the progress mutt was creating a very large tmp file in /tmp/ until "memfree" reached a watermark then failed with a message like " no space in /tmp" sounds like I can't use mutt if my mutt mail file is close to the physical memory I have when tmp-on-tmpfs is enabled.. hmm....make sens? maybe we can't use tmp-on-tmpfs feature in f18 -- 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/