From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266005AbUHFQuL (ORCPT ); Fri, 6 Aug 2004 12:50:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268185AbUHFQrI (ORCPT ); Fri, 6 Aug 2004 12:47:08 -0400 Received: from rwcrmhc13.comcast.net ([204.127.198.39]:16358 "EHLO rwcrmhc13.comcast.net") by vger.kernel.org with ESMTP id S268191AbUHFQqA (ORCPT ); Fri, 6 Aug 2004 12:46:00 -0400 Subject: Re: [proc.txt] Fix /proc/pid/statm documentation From: Albert Cahalan To: William Lee Irwin III Cc: Roger Luethi , linux-kernel mailing list , linux-mm@kvack.org In-Reply-To: <20040806154834.GL17188@holomorphy.com> References: <1091754711.1231.2388.camel@cube> <20040806094037.GB11358@k3.hellgate.ch> <1091797122.1231.2452.camel@cube> <20040806154834.GL17188@holomorphy.com> Content-Type: text/plain Organization: Message-Id: <1091801683.1231.2467.camel@cube> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 06 Aug 2004 10:14:43 -0400 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2004-08-06 at 11:48, William Lee Irwin III wrote: > On Fri, 2004-08-06 at 05:40, Roger Luethi wrote: > >> And then there is the trade-off between human readable and > >> easy to parse. ISTR there have been occasional discussions, but maybe > >> it's time to revisit the issue because the current mess is a problem. > > On Fri, Aug 06, 2004 at 08:58:43AM -0400, Albert Cahalan wrote: > > The current bugs are a problem. > > Quoting your other email now: > > Could you describe those in isolation from other issues? Whatever Roger found, plus: 1. trs == text RESIDENT size 2. drs == data RESIDENT size 3. memory-mapped devices should be counted for only 1 file (use an old Linux box running X to see) I'm not terribly concerned right now. I just don't think it's OK to go ripping out statm over a few bugs. If we ripped out every buggy piece of kernel code, we'd have a 0-byte kernel. There are far bigger issues elsewhere, like %CPU.