public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Neil Brown <neilb@suse.de>
Cc: Theodore Tso <tytso@mit.edu>,
	Eric Hopper <hopper@omnifarious.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Question about Reiser4
Date: Mon, 23 Apr 2007 17:21:02 -0700	[thread overview]
Message-ID: <462D4D6E.50809@zytor.com> (raw)
In-Reply-To: <17965.19438.292138.959036@notabene.brown>

Neil Brown wrote:
> 
> Our you could think outside the circle:
> Store all your "small files" as symlinks, then use "symlink" to create
> them and "readlink" to read them. (You would probably end up use
> symlinkat and readlinkat).
> Only one system call instead of three.
> I guess you don't get meaningful permission bits then... I wonder if
> that really matters.
> 

For some applications, oh yes it does.

	-hpa

  reply	other threads:[~2007-04-24  0:23 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23  2:00 Question about Reiser4 Eric Hopper
2007-04-23  2:31 ` Lee Revell
2007-04-23  3:56 ` Rik van Riel
2007-04-23  3:56   ` William Heimbigner
2007-04-23  5:47     ` Rik van Riel
2007-04-23  5:57       ` William Heimbigner
2007-04-23  6:07         ` Rik van Riel
2007-04-23  6:14           ` William Heimbigner
2007-04-23  6:20             ` Rik van Riel
2007-04-23  6:42               ` William Heimbigner
2007-04-23  8:04                 ` Andrew Morton
2007-04-23 11:31                   ` l.genoni
2007-04-23 13:52                   ` Eric Hopper
2007-04-23 17:40                     ` Andrew Morton
2007-04-23 18:36                       ` Miguel Ojeda
2007-04-23 19:05                       ` Andi Kleen
2007-04-23 22:56                     ` Theodore Tso
2007-04-23 23:53                       ` H. Peter Anvin
2007-04-24  0:14                         ` Neil Brown
2007-04-24  0:21                           ` H. Peter Anvin [this message]
2007-04-24 13:30                             ` Jan Engelhardt
2007-04-24  0:19                         ` Theodore Tso
2007-04-24  0:31                           ` H. Peter Anvin
2007-04-24  1:17                             ` Theodore Tso
2007-04-24 11:15                               ` Denis Vlasenko
2007-04-25  6:39                           ` Eric M. Hopper
2007-04-25 14:45                             ` lkml777
2007-04-23  6:14         ` Jeff Chua
     [not found] <20070423111939.c876c9cc.akpm@linux-foundation.org>
2007-04-24 14:43 ` Edward Shishkin
2007-04-24 19:39   ` Andi Kleen
2007-04-25 14:35     ` Edward Shishkin
2007-04-25 14:49       ` Jeff Chua
2007-04-25 15:06         ` lkml777
2007-04-25 15:50           ` Jeff Chua
2007-04-26  5:05             ` lkml777
2007-04-26  6:49               ` Jeff Chua
2007-04-26  5:09         ` lkml777
2007-04-26  6:48           ` Jeff Chua
2007-04-26  8:18             ` Jeff Chua
2007-04-27  7:16               ` lkml777
2007-04-26  0:44       ` lkml777
2007-04-25  0:12   ` lkml777
2007-04-25  6:26     ` Eric M. Hopper
2007-04-25 15:03     ` Edward Shishkin
2007-04-26  7:47     ` lkml777
2007-04-26  7:54     ` lkml777
2007-05-02  2:39   ` lkml777
2007-05-02  4:53   ` lkml777

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=462D4D6E.50809@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=hopper@omnifarious.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tytso@mit.edu \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox