From: "Martin K. Petersen" <mkp@mkp.net>
To: Svetoslav Slavtchev <galia@st-peter.stw.uni-erlangen.de>
Cc: Stephen Lord <lord@sgi.com>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: 2.4.18-rc4-aa1 XFS oopses caused by cpio
Date: 08 Mar 2002 14:14:36 -0500 [thread overview]
Message-ID: <yq13czax46b.fsf@austin.mkp.net> (raw)
In-Reply-To: <1015580766.20800.3.camel@svetljo.st-peter.stw.uni-erlangen.de> <3C88B612.1070206@sgi.com> <3C88C9A1.5070502@st-peter.stw.uni-erlangen.de> <3C88CB1C.90203@sgi.com> <1015613123.4301.11.camel@svetljo.st-peter.stw.uni-erlangen.de>
In-Reply-To: <1015613123.4301.11.camel@svetljo.st-peter.stw.uni-erlangen.de>
>>>>> "Svetoslav" == Svetoslav Slavtchev <galia@st-peter.stw.uni-erlangen.de> writes:
Svetoslav> and a stupid question is there a way to limit the I/O
Svetoslav> request that XFS sends to the lower layer ( soft RAID or
Svetoslav> lvm ) without need to modify existing fs just a hack until
Svetoslav> the raid-0 code in 2.5 is fixed
Not really. Besides, requests may be merged and that would give the
same result.
I've been busy with IA-64 stuff the last week - I'll try to get back
to the RAID hacking this weekend. I have all of my code merged but
still need to deal with multi-zone setups.
--
Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc.
mkp@linuxcare.com, http://www.linuxcare.com/
SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/
prev parent reply other threads:[~2002-03-08 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 9:46 2.4.18-rc4-aa1 XFS oopses caused by cpio Svetoslav Slavtchev
2002-03-08 13:01 ` Stephen Lord
2002-03-08 14:24 ` svetljo
2002-03-08 14:30 ` Stephen Lord
2002-03-08 15:59 ` Stephen Lord
2002-03-10 22:19 ` Pavel Machek
2002-03-08 18:45 ` Svetoslav Slavtchev
2002-03-08 19:14 ` Martin K. Petersen [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=yq13czax46b.fsf@austin.mkp.net \
--to=mkp@mkp.net \
--cc=galia@st-peter.stw.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@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