From: xerofoify@gmail.com (Nicholas Krause)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel Locking Question
Date: Wed, 11 Mar 2015 19:03:33 -0400 [thread overview]
Message-ID: <5F652017-F161-46C2-9DAC-B2341C463832@gmail.com> (raw)
Greetings All,
After learning about kernel locking and how atomic operations are good in terms of improving CPU scalability in terms of making a critical region much smaller. I
was wondering of how this would improve file system scalability and reliability if implemented in file system code for btrfs worker threads.
Nick
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next reply other threads:[~2015-03-11 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 23:03 Nicholas Krause [this message]
2015-03-12 1:48 ` Kernel Locking Question Valdis.Kletnieks at vt.edu
2015-03-12 4:42 ` nick
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=5F652017-F161-46C2-9DAC-B2341C463832@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).