Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755686Ab0FXOsa (ORCPT ); Thu, 24 Jun 2010 10:48:30 -0400 Received: from fxip-0047f.externet.hu ([88.209.222.127]:51260 "EHLO pomaz-ex.szeredi.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755464Ab0FXOs2 (ORCPT ); Thu, 24 Jun 2010 10:48:28 -0400 To: Andrew Lutomirski CC: miklos@szeredi.hu, npiggin@suse.de, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk, drepper@redhat.com, torvalds@linux-foundation.org In-reply-to: (message from Andrew Lutomirski on Thu, 24 Jun 2010 10:37:31 -0400) Subject: Re: [rfc] new stat*fs-like syscall? References: <20100624131455.GA10441@laptop> <4C2366F7.5010200@mit.edu> Message-Id: From: Miklos Szeredi Date: Thu, 24 Jun 2010 16:48:20 +0200 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 717 Lines: 19 On Thu, 24 Jun 2010, Andrew Lutomirski wrote: > Wasn't the point that /proc/self/mounts (and presumably > /proc/self/mountinfo) isn't scalable and we wanted a syscall to query > it efficiently (and racelessly)? The question was how to support statvfs() efficiently, and the only thing missing there is f_flags which can easily be added to the existing statfs() syscall. A separate mount_info() syscall might possibly be useful, but that's another story. Thanks, Miklos -- 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/