public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark <musicman529@yahoo.com>
To: xfs@oss.sgi.com
Subject: XFS mkfs/mount options
Date: Tue, 17 Jun 2008 00:33:57 -0700 (PDT)	[thread overview]
Message-ID: <881489.19090.qm@web34506.mail.mud.yahoo.com> (raw)

I have been doing some experiments with XFS on my "hot new desktop system," and I have turned up an interesting bit of info. (Note: My system is an AMD64 X2 2.5GHz running Linux.)

When I mount an XFS volume (thus loading the xfs kernel module), the kernel spawns two CPU-bound threads for "xfslogd" and "xfsdatad". However, it appears that only one of each of these kernel processes is getting any load, as indicated by "ps ax":

 3700 ?        S<     0:00 [xfslogd/0]
 3701 ?        S<     0:19 [xfslogd/1]
 3702 ?        S<     0:00 [xfsdatad/0]
 3703 ?        D<     0:05 [xfsdatad/1]

For each of these kernel threads, only those on CPU #2 are actually pulling notable load. Why is this?

I understand that I may have overlooked some critical tidbit of info in the man pages, or perhaps I have not yet found something online that could explain a default limitation. If so, I would very much enjoy new information about using XFS on a desktop system.

TYIA for your answer(s).

-- 
Mark

"What better place to find oneself than
 on the streets of one's home village?"
      --Capt. Jean-Luc Picard, "Family"

             reply	other threads:[~2008-06-17  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-17  7:33 Mark [this message]
2008-06-17  7:41 ` XFS mkfs/mount options Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2008-06-17  9:20 Mark
2008-06-17 12:27 ` Justin Piszcz
2008-06-17 17:29 Mark
2008-06-17 20:41 ` 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=881489.19090.qm@web34506.mail.mud.yahoo.com \
    --to=musicman529@yahoo.com \
    --cc=xfs@oss.sgi.com \
    /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