public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nikolay S." <nowhere@hakkenden.ath.cx>
To: xfs@oss.sgi.com
Subject: xfs_inode slab
Date: Sun, 10 Feb 2013 11:14:09 +0400	[thread overview]
Message-ID: <1360480449.4034.8.camel@hakkenden.homenet> (raw)

Hello there,

I see some bad behavior of xfs, which I can reproduce:

1. Create some directories and files on xfs volume (I use ~800000 files
and 80000 directories on 4GB RAM system)
2. Create workload, that produces light page cache pressure (say, 4-8
MB/s) and while pagecache eats all of free ram. I use the code from [1])
3. Stat all the objects on xfs volume

The result depends on kernel version:
	3.2) See kswapd struggling through D-state for several minutes.
	3.7) See kswapd struggling through D-state forever

Same steps on ext4 do not produce any bad results

--
[1]	https://bugzilla.kernel.org/show_bug.cgi?id=53031

[2]


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2013-02-10  7:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10  7:14 Nikolay S. [this message]
2013-02-10 21:06 ` xfs_inode slab Dave Chinner

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=1360480449.4034.8.camel@hakkenden.homenet \
    --to=nowhere@hakkenden.ath.cx \
    --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