From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Hans Reiser <reiser@namesys.com>
Cc: Cyrille Chepelov <cyrille@chepelov.org>, reiserfs-list@namesys.com
Subject: Re: FIFO files
Date: Tue, 17 Jun 2003 19:00:25 +0200 [thread overview]
Message-ID: <3EEF4929.20503@gmx.net> (raw)
In-Reply-To: <3EEF42B6.1000409@namesys.com>
Hans Reiser wrote:
> Carl-Daniel Hailfinger wrote:
>> Cyrille Chepelov wrote:
>>
>>> I recently encountered a need for such a contraption as file-backed
>>> FIFOs. These are files where one process can append records at one
>>> end, and one other process can read records from the beginning of
>>> the file, chopping off the head of the file once it's not needed
>>> anymore. As I had to implement something right now on existing
>>> systems, I worked around the general absence
>>
>> This facility has been present in linux for years. Just google for
>> "sparse files".
>
> No, he is resetting the location of the first byte of the file.
Yes, but if I understood Cyrille correctly, her/his(?) needs should be
completely satisfied by sparse files.
One process can append records at the end, and one other process can read
records from the beginning of the file, marking the read data empty. The
disk usage is the same as with Cyrille's solution, but the races are avoided.
The only reason I know for wanting to chop off the head of a file is
trying to keep the file small.
Carl-Daniel
next prev parent reply other threads:[~2003-06-17 17:00 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 [this message]
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
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=3EEF4929.20503@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=cyrille@chepelov.org \
--cc=reiser@namesys.com \
--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.