9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] [PATCH] fossil: fix a deadlock in the caching logic
Date: Sat, 8 Apr 2023 09:50:15 +0200	[thread overview]
Message-ID: <CAFSF3XMksdGaUg7j2O6HtYOa0oHG6xCVSb404zRp5+7G9Zt_+w@mail.gmail.com> (raw)
In-Reply-To: <CAJQ9t7j=y2NM1+sWhrG28UoHsDnuywNEc9h0xkjbKc35OX=02g@mail.gmail.com>

fixing another couple deadlocks makes you finally consider ditching fossil?
zfs storage isn't always permanent either, for example if you use
encryption or deduplication.

On 4/6/23, Lucio De Re <lucio.dere@gmail.com> wrote:
> On 4/6/23, noam@pixelhero.dev <noam@pixelhero.dev> wrote:
>> Quoth Charles Forsyth <charles.forsyth@gmail.com>:
>>> fussing about certain things for hard drives that probably don't matter
>>> for
>>> SSD let alone nvme
>>
>> I am once again asking you to be more specific, please :)
>>
>> I have Plans for improving venti for myself, it'd be great to actually
>> have a specific list of issues that others have noticed!
>>
> I presume that fossil doesn't apply special treatment to SSD and NVME
> which to my limited understand could be a serious downside. I guess
> I'm asking whether one should seriously consider ditching the
> fossil/venti combination and consider centralising permanent storage
> on something like ZFS instead?
> 
> Lucio.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T354fe702e1e9d5e9-Md68125af550af6687f52fa58
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2023-04-08  7:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 17:15 noam
2023-04-04 18:03 ` Steve Simon
2023-04-04 18:34   ` Skip Tavakkolian
2023-04-04 20:44     ` Charles Forsyth
2023-04-04 20:50       ` Charles Forsyth
2023-04-05  1:59         ` noam
2023-04-05 21:25           ` Charles Forsyth
2023-04-06  3:22             ` noam
2023-04-06  3:57               ` Lucio De Re
2023-04-08  7:50                 ` hiro [this message]
2023-04-08 14:30                   ` Charles Forsyth
2023-04-08 14:36                     ` Charles Forsyth
2023-04-08 15:09                       ` Dan Cross
2023-04-08 15:27                         ` Steffen Nurpmeso
2023-04-08 17:12                         ` Bakul Shah
2023-04-04 22:07       ` Anthony Martin
2023-04-05  2:48         ` noam
2023-04-04 22:15   ` noam

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=CAFSF3XMksdGaUg7j2O6HtYOa0oHG6xCVSb404zRp5+7G9Zt_+w@mail.gmail.com \
    --to=23hiro@gmail.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).