From: Hans Reiser <reiser@namesys.com>
To: Cyrille Chepelov <cyrille@chepelov.org>
Cc: reiserfs-list@namesys.com
Subject: Re: FIFO files
Date: Tue, 17 Jun 2003 23:30:57 +0400 [thread overview]
Message-ID: <3EEF6C71.7060303@namesys.com> (raw)
In-Reply-To: <20030617170720.GC14124@chepelov.org>
Cyrille Chepelov wrote:
>Le Tue, Jun 17, 2003, à 06:24:19PM +0200, Carl-Daniel Hailfinger a écrit:
>
>
>
>>This facility has been present in linux for years. Just google for "sparse
>>files".
>>
>>
>
>Yes sparse files would do. However, after a sizeable use of the facility,
>you'd end up with a giant hole at the beginning, whatever queued data, and
>EOF.
>What I want to do is the ability to just remove the hole in front (just as
>when there is no point in having a hole at the end of the file, you just
>truncate that hole out), so that seek(SEEK_BEGIN,0) positions me at the
>beginning of useful data (or EOF if my queue is empty).
>
> -- Cyrille
>
>
>
So in answer, yes, this is quite feasible and reasonable to do. I will
be likely to accept such a patch, though you should send a detailed
design first to reiserfs-list before writing code.
--
Hans
next prev parent reply other threads:[~2003-06-17 19:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 16:21 FIFO files Cyrille Chepelov
2003-06-17 16:24 ` Carl-Daniel Hailfinger
2003-06-17 16:32 ` Hans Reiser
2003-06-17 17:00 ` Carl-Daniel Hailfinger
2003-06-18 6:17 ` Oleg Drokin
2003-06-18 10:20 ` Ragnar Kjørstad
2003-06-18 11:40 ` Carl-Daniel Hailfinger
2003-06-18 13:21 ` Hans Reiser
2003-06-18 13:53 ` David Woodhouse
2003-06-18 14:28 ` Matthew Wilcox
2003-06-18 15:23 ` Russell Coker
2003-06-18 15:40 ` David Woodhouse
2003-06-18 15:51 ` Bryan Henderson
2003-06-18 15:45 ` Bryan Henderson
2003-06-18 15:34 ` Bryan Henderson
2003-06-17 17:07 ` Cyrille Chepelov
2003-06-17 17:39 ` Chris Dukes
2003-06-17 17:54 ` Cyrille Chepelov
2003-06-17 19:30 ` Hans Reiser [this message]
2003-06-17 19:43 ` Cyrille Chepelov
2003-06-17 22:42 ` Pierre Abbat
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=3EEF6C71.7060303@namesys.com \
--to=reiser@namesys.com \
--cc=cyrille@chepelov.org \
--cc=reiserfs-list@namesys.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.