From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] userspace netlog style log file in fs?
Date: Mon, 3 Oct 2005 14:02:01 -0400 [thread overview]
Message-ID: <ee9e417a0510031102v41866cd0s34920e238a140cdd@mail.gmail.com> (raw)
In-Reply-To: <200510031748.j93HmA806250@zamenhof.cs.utwente.nl>
> I guess this amounts to
> - keeping a ring buffer of log messages (a la netlog)
> - keeping a queue of 'pending' read's --
> read is the only thing for which completion
> may have to be delayed, right?
Yes.
> - pending reads should 'complete' when stuff
> is logged (i.e. something to read appears)
> - pending reads should be cleaned away
> when the fid is clunked
> - deal with flushes?
Yes! Otherwise you can't kill a process that is blocked
reading the log file.
> - deal with slow readers that read slower
> than the log gets updated, i.e. at a certain
> moment they may ask for data that already has
> been overwritten
Tough for them.
> I found inspiration in /sys/src/9/ip/netlog.c and
> /sys/src/cmd/ssh/sshnet.c
See also /sys/src/9/port/log.c. Sshnet is a good example
of getting the flushes right.
Russ
prev parent reply other threads:[~2005-10-03 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 17:48 Axel Belinfante
2005-10-03 18:02 ` Russ Cox [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=ee9e417a0510031102v41866cd0s34920e238a140cdd@mail.gmail.com \
--to=rsc@swtch.com \
--cc=9fans@cse.psu.edu \
/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).