From: Joel Becker <jlbec@evilplan.org>
To: Josef Bacik <josef@redhat.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
Tristan Ye <tristan.ye@oracle.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
chris.mason@oracle.com, tm@tao.ma
Subject: Re: [Ocfs2-devel] [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().
Date: Fri, 1 Apr 2011 09:54:58 -0700 [thread overview]
Message-ID: <20110401165458.GA25355@noexit> (raw)
In-Reply-To: <20110401003450.GD7484@dhcp231-156.rdu.redhat.com>
On Thu, Mar 31, 2011 at 08:34:50PM -0400, Josef Bacik wrote:
> > More interesting would be to bring the ioctls up to generic code
> > and have them backended by fallocate. I'm not sure they map without
> > looking deeper, but it's at least an idea.
> >
>
> I just did a cursory look and it seems like that would work out ok. Thanks,
Note that ocfs2 and xfs have identical ioctl values (ocfs2
copied xfs's on purpose).
Joel
--
Life's Little Instruction Book #306
"Take a nap on Sunday afternoons."
http://www.jlbec.org/
jlbec@evilplan.org
WARNING: multiple messages have this Message-ID (diff)
From: Joel Becker <jlbec@evilplan.org>
To: Josef Bacik <josef@redhat.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
Tristan Ye <tristan.ye@oracle.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
chris.mason@oracle.com, tm@tao.ma
Subject: [Ocfs2-devel] [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().
Date: Fri, 1 Apr 2011 09:54:58 -0700 [thread overview]
Message-ID: <20110401165458.GA25355@noexit> (raw)
In-Reply-To: <20110401003450.GD7484@dhcp231-156.rdu.redhat.com>
On Thu, Mar 31, 2011 at 08:34:50PM -0400, Josef Bacik wrote:
> > More interesting would be to bring the ioctls up to generic code
> > and have them backended by fallocate. I'm not sure they map without
> > looking deeper, but it's at least an idea.
> >
>
> I just did a cursory look and it seems like that would work out ok. Thanks,
Note that ocfs2 and xfs have identical ioctl values (ocfs2
copied xfs's on purpose).
Joel
--
Life's Little Instruction Book #306
"Take a nap on Sunday afternoons."
http://www.jlbec.org/
jlbec at evilplan.org
next prev parent reply other threads:[~2011-04-01 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 7:33 [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl() Tristan Ye
2011-03-31 7:33 ` [Ocfs2-devel] " Tristan Ye
2011-03-31 21:14 ` Sunil Mushran
2011-03-31 21:14 ` Sunil Mushran
2011-03-31 21:14 ` [Ocfs2-devel] " Sunil Mushran
2011-03-31 22:56 ` Josef Bacik
2011-03-31 22:56 ` [Ocfs2-devel] " Josef Bacik
2011-03-31 23:44 ` Joel Becker
2011-03-31 23:44 ` [Ocfs2-devel] " Joel Becker
2011-04-01 0:34 ` Josef Bacik
2011-04-01 0:34 ` Josef Bacik
2011-04-01 0:34 ` [Ocfs2-devel] " Josef Bacik
2011-04-01 16:54 ` Joel Becker [this message]
2011-04-01 16:54 ` Joel Becker
2011-04-01 0:34 ` Josef Bacik
-- strict thread matches above, loose matches on Subject: below --
2011-03-31 7:34 [Ocfs2-devel] " Tristan Ye
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=20110401165458.GA25355@noexit \
--to=jlbec@evilplan.org \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sunil.mushran@oracle.com \
--cc=tm@tao.ma \
--cc=tristan.ye@oracle.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.