From: Nick Krause <xerofoify@gmail.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org SYSTEM list:BTRFS FILE"
<linux-btrfs@vger.kernel.org>
Subject: Multi Core Support for compression in compression.c
Date: Sun, 27 Jul 2014 16:47:52 -0400 [thread overview]
Message-ID: <CAPDOMViXEgN1U8Og52Fd7EaM86Ad2Dfex9TVQ-+tRZ9SL9Kcig@mail.gmail.com> (raw)
This may be a bad idea , but compression in brtfs seems to be only
using one core to compress.
Depending on the CPU used and the amount of cores in the CPU we can
make this much faster
with multiple cores. This seems bad by my reading at least I would
recommend for writing compression
we write a function to use a certain amount of cores based on the load
of the system's CPU not using
more then 75% of the system's CPU resources as my system when idle has
never needed more
then one core of my i5 2500k to run when with interrupts for opening
eclipse are running. For reading
compression on good core seems fine to me as testing other compression
software for reads , it's
way less CPU intensive.
Cheers Nick
next reply other threads:[~2014-07-27 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 20:47 Nick Krause [this message]
2014-07-28 2:56 ` Multi Core Support for compression in compression.c Austin S Hemmelgarn
2014-07-28 3:21 ` Nick Krause
2014-07-28 10:02 ` Hugo Mills
2014-07-28 10:10 ` Austin S Hemmelgarn
2014-07-28 15:13 ` Nick Krause
2014-07-28 15:57 ` Nick Krause
2014-07-28 16:19 ` Austin S Hemmelgarn
2014-07-28 18:36 ` Nick Krause
2014-07-29 17:08 ` Nick Krause
2014-07-29 17:14 ` Austin S Hemmelgarn
2014-07-29 17:38 ` Nick Krause
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=CAPDOMViXEgN1U8Og52Fd7EaM86Ad2Dfex9TVQ-+tRZ9SL9Kcig@mail.gmail.com \
--to=xerofoify@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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).