From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Questions about btrfs helper threads
Date: Mon, 25 Aug 2014 12:24:37 -0400 [thread overview]
Message-ID: <53FB6345.1030301@gmail.com> (raw)
In-Reply-To: <6109.1408945968@turing-police.cc.vt.edu>
On 14-08-25 01:52 AM, Valdis.Kletnieks at vt.edu wrote:
> On Sun, 24 Aug 2014 23:31:38 -0400, nick said:
>> In addition , why not create a linked list for the compression in btrfs as we
>> can then do the work using the already build in workqueues for btrfs and
>> improve the scalability of the compression functions and workload it causes as
>> compression is very CPU intensive and we can easily take advance of workquenes
>> in order to allow then to run when idle or rarely when CPU is under heavy load.
>
> Because fsync() exists.
>
>
About my other question how many cores is btrfs scaling to? I would like to known for reasons of understanding
the more strict locking I am finding in the btrfs code.
Nick
prev parent reply other threads:[~2014-08-25 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 5:49 Questions about btrfs helper threads nick
2014-08-24 15:22 ` Valdis.Kletnieks at vt.edu
2014-08-25 2:21 ` nick
2014-08-25 3:31 ` nick
2014-08-25 5:52 ` Valdis.Kletnieks at vt.edu
2014-08-25 16:24 ` nick [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=53FB6345.1030301@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).