LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Ulrich Drepper <drepper@redhat.com>, Neil Brown <neilb@suse.de>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] utimensat implementation
Date: Thu, 10 May 2007 12:44:19 -0700 [thread overview]
Message-ID: <46437613.4060407@redhat.com> (raw)
In-Reply-To: <20070510185226.GA1458@infradead.org>
Christoph Hellwig wrote:
> E.g.
>
> long foofs_pathconf {
> [_PC_LINK_MAX] = 16384,
> [_PC_2_SYMLINKS] = 1,
In general I agree. But what do you do for network filesystems? Maybe
we'll have a network filesystem protocol which allows to query the
remote server about the underlying filesystem. Then the return value is
dynamic and it's the maximum (coarsest granularity) of the network
filesystem itself and the underlying filesystem.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
next prev parent reply other threads:[~2007-05-10 19:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 22:49 Ulrich Drepper
2007-04-26 23:25 ` Andrew Morton
2007-04-27 0:11 ` H. Peter Anvin
2007-04-27 0:55 ` Ulrich Drepper
2007-04-27 0:58 ` H. Peter Anvin
2007-04-27 1:04 ` Ulrich Drepper
2007-04-27 23:15 ` H. Peter Anvin
2007-04-27 23:05 ` David Lang
2007-04-27 23:30 ` Ulrich Drepper
2007-04-27 23:33 ` H. Peter Anvin
2007-04-27 0:54 ` Ulrich Drepper
2007-04-27 15:27 ` Updated utimensat test program Ulrich Drepper
2007-04-27 1:57 ` [PATCH] utimensat implementation Neil Brown
2007-04-27 2:13 ` Ulrich Drepper
2007-04-27 6:01 ` Neil Brown
2007-05-10 18:26 ` Ulrich Drepper
2007-05-10 18:52 ` Christoph Hellwig
2007-05-10 19:44 ` Ulrich Drepper [this message]
2007-05-13 21:02 ` Christoph Hellwig
2007-05-11 1:01 ` H. Peter Anvin
2007-05-11 2:14 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46437613.4060407@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--subject='Re: [PATCH] utimensat implementation' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).