From: Matthew Wilcox <matthew@wil.cx>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt)
Date: Fri, 23 Mar 2001 17:16:13 +0000 [thread overview]
Message-ID: <20010323171613.H5491@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <OF791BBBC5.E3FCBEEE-ON87256A18.005BA3B7@LocalDomain>
In-Reply-To: <OF791BBBC5.E3FCBEEE-ON87256A18.005BA3B7@LocalDomain>; from hbryan@us.ibm.com on Fri, Mar 23, 2001 at 09:56:47AM -0700
On Fri, Mar 23, 2001 at 09:56:47AM -0700, Bryan Henderson wrote:
> There's a lot of cool simplicity in this, both in implementation and
> application, but it leaves something to be desired in functionality. This
> is partly because the price you pay for being able to use existing,
> well-worn Unix interfaces is the ancient limitations of those interfaces
> -- like the inability to return adequate error information.
hmm... open("defrag-error") first, then read from it if it fails?
> effective the defrag was? And bear in mind that multiple processes may be
> issuing commands to /mnt/control simultaneously.
you should probably serialise them. you probably have to do this anyway.
> With ioctl, I can easily match a response of any kind to a request. I can
> even return an English text message if I want to be friendly.
yes, one of the nice plan9 changes was the change to returning strings
instead of numerics.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-03-23 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 16:56 [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Bryan Henderson
2001-03-23 17:16 ` Matthew Wilcox [this message]
2001-03-23 18:28 ` Alexander Viro
2001-03-23 17:35 ` Pjotr Kourzanoff
2001-04-01 9:01 ` Chip Salzenberg
2001-04-01 11:48 ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentatio Kai Henningsen
2001-04-01 12:50 ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Keith Owens
2001-04-02 19:49 ` Chip Salzenberg
2001-04-10 7:51 ` Tommi Virtanen
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 22:06 [PATCH] Documentation/ioctl-number.txt Dave Kleikamp
2001-03-22 23:07 ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Alexander Viro
2001-03-23 6:00 ` Andreas Dilger
2001-03-23 12:06 ` Alexander Viro
2001-03-23 14:45 ` Eric W. Biederman
2001-03-23 16:15 ` [RFC] sane access to per-fs metadata (was Re: [PATCH]Documentation/ioctl-number.txt) Dave Kleikamp
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=20010323171613.H5491@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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