linux-bcachefs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: Questions related to BCacheFS
Date: Sun, 19 Nov 2023 00:15:19 +0100	[thread overview]
Message-ID: <4197014.1IzOArtZ34@lichtvoll.de> (raw)
In-Reply-To: <20231118210727.6s7bi3e4lldnrpoj@moria.home.lan>

Thanks again, Kent.

Kent Overstreet - 18.11.23, 22:07:27 CET:
> > As far as I understand one specific performance related aspect of
> > BCacheFS would be low latencies due to the frontend / backend
> > architecture which in principle is based on what has been there in
> > BCache already. I am intending to explore a bit into that concept in
> > my article.
> 
> The low latency stuff actually wasn't in bcache - that work came later.

So the frontend / backend architecture is not that much of what makes 
BCacheFS unique? Important to know as it seems I may have misunderstood 
something here.

I may need to shift the approach to my article a bit then. Good that I 
asked early on.

-- 
Martin



  reply	other threads:[~2023-11-18 23:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18 19:15 Questions related to BCacheFS Martin Steigerwald
2023-11-18 19:50 ` Kent Overstreet
2023-11-18 20:57   ` Martin Steigerwald
2023-11-18 21:07     ` Kent Overstreet
2023-11-18 23:15       ` Martin Steigerwald [this message]
2023-11-18 23:42         ` Kent Overstreet
2023-11-19 11:13           ` Martin Steigerwald
2023-11-19 16:43             ` Martin Steigerwald
2023-11-19 23:10             ` Kent Overstreet
2023-11-20 17:34               ` Martin Steigerwald
2023-12-03 16:58               ` Martin Steigerwald
2023-12-18 16:50                 ` Martin Steigerwald
2023-12-28 22:29     ` deletion time of big files (was: Re: Questions related to BCacheFS) Martin Steigerwald
2023-12-29 18:48       ` Kent Overstreet
2023-12-30 10:51         ` Martin Steigerwald

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=4197014.1IzOArtZ34@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    /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).