All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Ben Myers <bpm@sgi.com>, Alex Elder <elder@kernel.org>, xfs@oss.sgi.com
Subject: global serialization points in XFS circa 2.6.27?
Date: Thu, 13 Sep 2012 17:23:33 -0600	[thread overview]
Message-ID: <50526AF5.50201@genband.com> (raw)


Hi,

I've got an embedded system running a modified 2.6.27 (yes, we're trying 
to upgrade) and we're running into a scenario where something is 
happening that causes accesses to *all* XFS filesystems to hang or be 
delayed for some time.

I know it may be a bit of a stretch since the kernel is old, but I was 
wondering if you might have any suggestions as to what I might look at 
as far as locks/algorithms within XFS that would affect all filesystems.

In case it matters, the hardware is fairly beefy-- 32 threads of Sandy 
Bridge CPU, 64GB RAM, SAS drives, etc.

Chris

-- 

Chris Friesen
Software Designer

3500 Carling Avenue
Ottawa, Ontario K2H 8E9
www.genband.com

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

                 reply	other threads:[~2012-09-13 23:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=50526AF5.50201@genband.com \
    --to=chris.friesen@genband.com \
    --cc=bpm@sgi.com \
    --cc=elder@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.