From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 105121] lseek(SEEK_DATA) hangs for a long time for sparse files in the page cache
Date: Mon, 28 Sep 2015 15:15:29 +0000 [thread overview]
Message-ID: <bug-105121-13602-AQKdWQF0gI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-105121-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=105121
--- Comment #3 from Theodore Tso <tytso@mit.edu> ---
This implies that grep is using lseek(SEEK_DATA) as an optimization when users
use grep on sparse files. So I'm guessing this is a Thing, but I'm at a loss
why people are interested in running grep on a sparse file (with or without
blocks preallocated using fallocate). Can you enlighten me as to why people
(or at least you and your colleague) find it useful to run grep on such files?
Not that it matters since this is a pretty clear optimization we should add to
ext4; I'm just curious what the use case is.
Thanks!!
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-09-28 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 12:27 [Bug 105121] New: lseek() hangs for a long time on allocated files bugzilla-daemon
2015-09-28 14:37 ` [Bug 105121] lseek(SEEK_DATA) hangs for a long time for sparse files in the page cache bugzilla-daemon
2015-09-28 14:47 ` bugzilla-daemon
2015-09-28 14:52 ` bugzilla-daemon
2015-09-28 15:15 ` bugzilla-daemon [this message]
2015-09-28 15:23 ` bugzilla-daemon
2019-01-18 7:44 ` bugzilla-daemon
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=bug-105121-13602-AQKdWQF0gI@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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