XFS mkfs/mount options
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).
Signature · 5 lines
Mark
"What better place to find oneself than
on the streets of one's home village?"
--Capt. Jean-Luc Picard, "Family"Quoted 9 lines · Mark
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":
Quoted 6 lines
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?
Because your disk interrupts are delivered to that CPU only.
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]