From: Ankit Jain <me@ankitjain.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-kernel@vger.kernel.org, joel.becker@oracle.com,
Christoph Hellwig <hch@infradead.org>,
xfs-masters@oss.sgi.com, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
ocfs2-devel@oss.oracle.com
Subject: Re: [xfs-masters] [PATCH][RFC] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls
Date: Thu, 18 Dec 2008 15:20:29 +0530 [thread overview]
Message-ID: <494A1CE5.8020007@ankitjain.org> (raw)
In-Reply-To: <20081217211550.GF8791@wotan.suse.de>
Mark Fasheh wrote:
> On Wed, Dec 17, 2008 at 03:06:14PM -0600, Eric Sandeen wrote:
>
> Actually, yeah agreed - I take that back. Old users are already getting them
> from file system headers, new ones should use fallocate. So there's no need
> to expose the ioctls to userspace, at least not if all we're talking about
> is the RESVP ioctls.
Makes sense. So I can just keep them in falloc.h in a #ifdef __KERNEL__ ? Or
should this be in a new ioctl.h ?
-Ankit
> --Mark
>
> --
> Mark Fasheh
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Ankit Jain <me@ankitjain.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-kernel@vger.kernel.org, joel.becker@oracle.com,
Christoph Hellwig <hch@infradead.org>,
xfs-masters@oss.sgi.com, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [xfs-masters] [PATCH][RFC] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls
Date: Thu, 18 Dec 2008 09:51:10 -0000 [thread overview]
Message-ID: <494A1CE5.8020007@ankitjain.org> (raw)
In-Reply-To: <20081217211550.GF8791@wotan.suse.de>
Mark Fasheh wrote:
> On Wed, Dec 17, 2008 at 03:06:14PM -0600, Eric Sandeen wrote:
>
> Actually, yeah agreed - I take that back. Old users are already getting them
> from file system headers, new ones should use fallocate. So there's no need
> to expose the ioctls to userspace, at least not if all we're talking about
> is the RESVP ioctls.
Makes sense. So I can just keep them in falloc.h in a #ifdef __KERNEL__ ? Or
should this be in a new ioctl.h ?
-Ankit
> --Mark
>
> --
> Mark Fasheh
WARNING: multiple messages have this Message-ID (diff)
From: Ankit Jain <me@ankitjain.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
linux-kernel@vger.kernel.org, joel.becker@oracle.com,
Christoph Hellwig <hch@infradead.org>,
xfs-masters@oss.sgi.com, Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
ocfs2-devel@oss.oracle.com
Subject: Re: [xfs-masters] [PATCH][RFC] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls
Date: Thu, 18 Dec 2008 15:20:29 +0530 [thread overview]
Message-ID: <494A1CE5.8020007@ankitjain.org> (raw)
In-Reply-To: <20081217211550.GF8791@wotan.suse.de>
Mark Fasheh wrote:
> On Wed, Dec 17, 2008 at 03:06:14PM -0600, Eric Sandeen wrote:
>
> Actually, yeah agreed - I take that back. Old users are already getting them
> from file system headers, new ones should use fallocate. So there's no need
> to expose the ioctls to userspace, at least not if all we're talking about
> is the RESVP ioctls.
Makes sense. So I can just keep them in falloc.h in a #ifdef __KERNEL__ ? Or
should this be in a new ioctl.h ?
-Ankit
> --Mark
>
> --
> Mark Fasheh
next prev parent reply other threads:[~2008-12-18 9:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 8:04 [PATCH][RFC] fs: Add new pre-allocation ioctls to vfs for compatibility with legacy xfs ioctls Ankit Jain
2008-12-15 8:04 ` Ankit Jain
2008-12-15 8:04 ` [Ocfs2-devel] " Ankit Jain
2008-12-17 20:28 ` Mark Fasheh
2008-12-17 20:28 ` Mark Fasheh
2008-12-17 20:28 ` [Ocfs2-devel] " Mark Fasheh
2008-12-17 21:06 ` [xfs-masters] " Eric Sandeen
2008-12-17 21:06 ` [Ocfs2-devel] " Eric Sandeen
2008-12-17 21:06 ` Eric Sandeen
2008-12-17 21:15 ` Mark Fasheh
2008-12-17 21:16 ` [Ocfs2-devel] " Mark Fasheh
2008-12-17 21:15 ` Mark Fasheh
2008-12-18 9:50 ` Ankit Jain [this message]
2008-12-18 9:51 ` [Ocfs2-devel] " Ankit Jain
2008-12-18 9:50 ` Ankit Jain
2008-12-18 9:44 ` Ankit Jain
2008-12-18 9:44 ` Ankit Jain
2008-12-18 9:44 ` [Ocfs2-devel] " Ankit Jain
2008-12-18 21:01 ` Ankit Jain
2008-12-18 21:01 ` Ankit Jain
2008-12-18 21:01 ` [Ocfs2-devel] " Ankit Jain
2008-12-18 6:49 ` Felix Blyakher
2008-12-18 6:52 ` [Ocfs2-devel] " Felix Blyakher
2008-12-18 6:49 ` Felix Blyakher
2008-12-18 9:54 ` Ankit Jain
2008-12-18 9:55 ` [Ocfs2-devel] " Ankit Jain
2008-12-18 9:54 ` Ankit Jain
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=494A1CE5.8020007@ankitjain.org \
--to=me@ankitjain.org \
--cc=hch@infradead.org \
--cc=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sandeen@sandeen.net \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.