From: Eric Sandeen <sandeen@sandeen.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Al Viro <viro@ftp.linux.org.uk>,
David Miller <davem@davemloft.net>,
dgc@sgi.com, jesper.juhl@gmail.com, chatz@melbourne.sgi.com,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
xfs-masters@oss.sgi.com, netdev@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networking, SMP
Date: Sun, 26 Nov 2006 08:31:29 -0600 [thread overview]
Message-ID: <4569A541.3030600@sandeen.net> (raw)
In-Reply-To: <1164269545.31358.771.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Thu, 2006-11-23 at 04:35 +0000, Al Viro wrote:
>>> I would even say 10 function calls deep to allocate file blocks
>>> is overkill, but 22 it just astronomically bad.
>> Especially since a large part is due to cxfs...
>> -
>
> it's a bit sad to see XFS this crippled in linux due to an external,
> proprietary module ;(
>
I understand that cxfs is a bit of a whipping-boy, but the stacks in
question in this thread really don't have much if anything to do with
the filesystem layering in xfs. They are deep callchains & large
functions in core xfs code, it seems.
-Eric
next prev parent reply other threads:[~2006-11-26 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a8748490611211551v2ebe88fel2bcf25af004c338a@mail.gmail.com>
[not found] ` <9a8748490611220458w4d94d953v21f7a29a9f1bdb72@mail.gmail.com>
[not found] ` <20061123011809.GY37654165@melbourne.sgi.com>
[not found] ` <20061122.201013.112290046.davem@davemloft.net>
[not found] ` <20061123043543.GI3078@ftp.linux.org.uk>
[not found] ` <1164269545.31358.771.camel@laptopd505.fenrus.org>
2006-11-23 22:08 ` [xfs-masters] Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs, scsi, networking, SMP Nathan Scott
2006-11-26 14:31 ` Eric Sandeen [this message]
[not found] <200611211027.41971.jesper.juhl@gmail.com>
2006-11-21 21:53 ` David Chatterton
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=4569A541.3030600@sandeen.net \
--to=sandeen@sandeen.net \
--cc=arjan@infradead.org \
--cc=chatz@melbourne.sgi.com \
--cc=davem@davemloft.net \
--cc=dgc@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
--cc=xfs-masters@oss.sgi.com \
--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