All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: Hans Reiser <reiser@namesys.com>,
	Cyrille Chepelov <cyrille@chepelov.org>,
	reiserfs-list@namesys.com
Subject: Re: FIFO files
Date: Wed, 18 Jun 2003 10:17:21 +0400	[thread overview]
Message-ID: <20030618061721.GA15283@namesys.com> (raw)
In-Reply-To: <3EEF4929.20503@gmx.net>

Hello!

On Tue, Jun 17, 2003 at 07:00:25PM +0200, Carl-Daniel Hailfinger wrote:
> 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

Hm, I am sorry, but this part is unclear.
I do not remember any API to create holes in existing files in place of already
present data.

Bye,
    Oleg

  reply	other threads:[~2003-06-18  6:17 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 [this message]
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=20030618061721.GA15283@namesys.com \
    --to=green@namesys.com \
    --cc=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.