From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/ioctl-number.txt
Date: Thu, 22 Mar 2001 16:06:47 -0600 [thread overview]
Message-ID: <3ABA7777.E2198DE9@austin.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0103221648380.5619-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> On Thu, 22 Mar 2001, Dave Kleikamp wrote:
>
> > Linus,
> > I would like to reserve a block of 32 ioctl's for the JFS filesystem.
>
> Details, please? More specifically, what kind of objects are these ioctls
> applied to?
I don't have all the details worked out yet, but the utilities to extend
and defragment the filesystem will operate on a live volume, so the
utilities will need to talk to the filesystem to move blocks, extend the
block map, etc.
The utilities will probably open the root directory and apply the ioctls
to it, unless there is a better way to do it.
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2001-03-22 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 21:20 [PATCH] Documentation/ioctl-number.txt Dave Kleikamp
2001-03-22 21:50 ` Alexander Viro
2001-03-22 22:06 ` Dave Kleikamp [this message]
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=3ABA7777.E2198DE9@austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.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