From: "Nicholas A. Bellinger" <nab@kernel.org>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Linux-iSCSI.org Target Dev"
<linux-iscsi-target-dev@googlegroups.com>
Subject: Re: [Announce]: Target_Core_Mod/ConfigFS and LIO-Target v3.0 work
Date: Sat, 13 Dec 2008 02:08:27 -0800 [thread overview]
Message-ID: <1229162907.4153.857.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <e2e108260812130141o3d21bbbdob9e7c9f95d309a74@mail.gmail.com>
On Sat, 2008-12-13 at 10:41 +0100, Bart Van Assche wrote:
> On Sat, Dec 13, 2008 at 7:20 AM, <Valdis.Kletnieks@vt.edu> wrote:
> > On Fri, 12 Dec 2008 01:40:09 PST, "Nicholas A. Bellinger" said:
> >
> >> Too bad, because you are missing out on the most advanced ConfigFS
> >> enabled storage engine on the planet.
> >
> > OK. I *have* to ask.. ;)
> >
> > What's the *second* most advanced configfs-enabled storage engine?
>
> Please don't let Nicholas Bellinger mislead you. The most important
> aspect of a storage engine is stability. Last January I ran
> performance tests on IET, STGT, SCST and LIO. I quickly found out not
> only that SCST had the highest throughput and the lowest latency, but
> also that the performance tests on LIO triggered several kernel
> crashes. I have reported these crashes to the linux-iscsi-target-dev
> mailing list, but even as of today, it's not yet clear whether all of
> these crashes have been fixed. During the last ten years I have filed
> bug reports for many open source projects, and the LIO project is the
> only project where the (kernel) crashes I reported were not addressed
> immediately.
>
> See also:
> * February 1, 2008, LIO kernel panic during configuration,
> http://groups.google.com/group/linux-iscsi-target-dev/browse_thread/thread/74c8b37f24b84e59/d94c07626bd20521?lnk=gst&q=kernel+panic#d94c07626bd20521.
> * February 8, 2008, kernel crash triggered by LIO,
> http://groups.google.com/group/linux-iscsi-target-dev/browse_thread/thread/30835aede1028188/5708e16a23367fb4?lnk=gst&q=kernel+crash#5708e16a23367fb4.
> * February 13, 2008, LIO target kernel code triggers memory
> corruption, http://groups.google.com/group/linux-iscsi-target-dev/browse_thread/thread/ddc1bf7666372972/2150a09f9ed3d1cd?lnk=gst&q=ipoib#2150a09f9ed3d1cd.
> * February 18, 2008, LIO target makes entire system hang,
> http://groups.google.com/group/linux-iscsi-target-dev/browse_thread/thread/6a76f9efd9409fc5/55bd8840b6a5f757?lnk=gst&q=lio+target+hangs#55bd8840b6a5f757.
>
Heh.
I have no idea why why you keep bringing up a minor BUG (completely
unrelated to Target_Core_Mod/ConfigFS and LIO-Target v3.0 btw) that was
fixed 10 months ago..? Perhaps if you spent half the time looking at
actual lio-core-2.6.git code that you do bringing up minor closed bugs
from months ago, you and Vlad would actually understand how ConfigFS
works by now.
Best Regards,
--nab
next prev parent reply other threads:[~2008-12-13 10:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 3:14 Nicholas A. Bellinger
2008-12-11 19:24 ` Bart Van Assche
2008-12-11 19:58 ` Nicholas A. Bellinger
2008-12-12 7:21 ` Bart Van Assche
2008-12-12 9:40 ` Nicholas A. Bellinger
2008-12-13 6:20 ` Valdis.Kletnieks
2008-12-13 8:27 ` Nicholas A. Bellinger
2008-12-13 9:41 ` Bart Van Assche
2008-12-13 10:08 ` Nicholas A. Bellinger [this message]
2008-12-13 10:23 ` Bart Van Assche
2008-12-13 11:18 ` Nicholas A. Bellinger
2008-12-13 11:56 ` Bart Van Assche
2008-12-13 12:33 ` Nicholas A. Bellinger
[not found] ` <e2e108260812130450y3288b32av7f435544823d9e97@mail.gmail.com>
2008-12-13 13:14 ` Nicholas A. Bellinger
2008-12-13 15:24 ` James Bottomley
2008-12-13 22:50 ` Nicholas A. Bellinger
2008-12-14 16:53 ` Bart Van Assche
2008-12-16 18:45 ` Vladislav Bolkhovitin
2008-12-13 15:35 ` Vladislav Bolkhovitin
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=1229162907.4153.857.camel@haakon2.linux-iscsi.org \
--to=nab@kernel.org \
--cc=bart.vanassche@gmail.com \
--cc=linux-iscsi-target-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®