From: "Ted Ts'o" <tytso@mit.edu>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A lot of [ext4-dio-unwrit] threads around
Date: Mon, 7 Feb 2011 13:05:24 -0500 [thread overview]
Message-ID: <20110207180524.GD3457@thunk.org> (raw)
In-Reply-To: <4D502746.4030500@pardus.org.tr>
On Mon, Feb 07, 2011 at 07:09:26PM +0200, Ozan Çağlayan wrote:
>
> This is 2.6.35.11 on a 24-core HP Proliant server with 8 mounted
> ext4 filesystems. There are 7 LXC containers which does heavy
> compiling workload during the day.
>
> Uptime is 3 days and currently there are 216 ext4-dio-unwrit threads
> in ps aux output? Is it normal or a symptom of a problem?
It's normal; the workqueues are created statically at mount time, one
per cpu per file system. There are some plans in train for a more
efficient way of dealing with workqueues in general on systems with
large numbers of CPU's, but for 2.6.35, yes, that's normal.
- Ted
prev parent reply other threads:[~2011-02-07 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 17:09 A lot of [ext4-dio-unwrit] threads around Ozan Çağlayan
2011-02-07 18:05 ` Ted Ts'o [this message]
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=20110207180524.GD3457@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
/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