From: Stan Hoeppner <stan@hardwarefreak.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: does having ~Ncore+1? kworkers flushing XFS to 1 disk improve throughput?
Date: Fri, 23 Aug 2013 23:07:48 -0500 [thread overview]
Message-ID: <52183194.2060008@hardwarefreak.com> (raw)
In-Reply-To: <52181B69.6060707@tlinx.org>
On 8/23/2013 9:33 PM, Linda Walsh wrote:
> So what are all the kworkers doing and does having 6 of them
> do things at the same time really help disk-throughput?
>
> Seems like they would conflict w/each other, cause
> disk contention, and extra fragmentation as they
> do things? If they were all writing to separate
> disks, that would make sense, but do that many kworker
> threads need to be finishing out disk I/O on 1 disk?
https://raw.github.com/torvalds/linux/master/Documentation/workqueue.txt
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-24 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 2:33 does having ~Ncore+1? kworkers flushing XFS to 1 disk improve throughput? Linda Walsh
2013-08-24 4:07 ` Stan Hoeppner [this message]
2013-08-24 17:18 ` Linda Walsh
2013-08-24 19:09 ` Stan Hoeppner
2013-08-24 23:22 ` Linda Walsh
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=52183194.2060008@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.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