9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Killing venti
Date: Thu,  5 Jan 2012 14:12:54 -0500	[thread overview]
Message-ID: <CADSkJJX_31dZkEWDPXUN7V-tzPgq-TrgW9MBF1fUmVM4Y9ymqw@mail.gmail.com> (raw)
In-Reply-To: <86wr96vyql.fsf@cmarib.ramside>

On Thu, Jan 5, 2012 at 12:35 PM,  <smiley@icebubble.org> wrote:
>> run venti/sync.
>
> Ah.  Cool.  Gotta love those undocumented commands.  :) While probing
> the distal edges of Venti's documented functionality, I also came across
> the following, which have similar (but not identical) effect:
>
> hget http://$vthost:$vtwebport/flushicache
> hget http://$vthost:$vtwebport/flushdcache
>
> These HTTP requests initiate flushes of the index and arena block
> caches, respectively, and don't return a response until the respective
> flush is complete.

Honestly, you don't even have to run venti/sync.
Every command that writes to venti ends by doing
a sync.

You probably don't want to use those hget commands.
They are safe, of course, but it is equally safe not to
run them.  The icache in particular can take a long time to
flush, and venti will recover the entries (in less time than
the flush would have taken) the next time it starts.

Russ


      parent reply	other threads:[~2012-01-05 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 17:21 smiley
2012-01-03 17:30 ` Russ Cox
2012-01-05 17:35   ` smiley
2012-01-05 18:21     ` David du Colombier
2012-01-06 17:20       ` smiley
2012-01-05 19:12     ` 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=CADSkJJX_31dZkEWDPXUN7V-tzPgq-TrgW9MBF1fUmVM4Y9ymqw@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).