From: Chris Wedgwood <cw@f00f.org>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Szakacsits Szabolcs <szaka@sienet.hu>,
linux@horizon.com, linux-fsdevel@vger.kernel.org
Subject: Re: SEEK_HOLE and SEEK_DATA
Date: Fri, 3 Feb 2006 15:53:23 -0800 [thread overview]
Message-ID: <20060203235323.GA11361@taniwha.stupidest.org> (raw)
In-Reply-To: <OFFFF96225.C7A5DF87-ON8825710A.00774348-8825710A.0078E7E9@us.ibm.com>
On Fri, Feb 03, 2006 at 02:00:31PM -0800, Bryan Henderson wrote:
> But dm_probe_hole() is considerably harder to use (as a programmer)
> than SEEK_HOLE/SEEK_DATA.
It's also not in mainline nor likely to ever get merged.
prev parent reply other threads:[~2006-02-03 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:03 SEEK_HOLE and SEEK_DATA linux
2006-02-03 18:08 ` Chris Wedgwood
2006-02-03 18:23 ` Szakacsits Szabolcs
2006-02-03 19:37 ` Chris Wedgwood
2006-02-03 22:00 ` Bryan Henderson
2006-02-03 23:41 ` Szakacsits Szabolcs
2006-02-03 23:53 ` Chris Wedgwood [this message]
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=20060203235323.GA11361@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=szaka@sienet.hu \
/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;
as well as URLs for NNTP newsgroup(s).