From: promo@starwindsoftware.com
To: fa.linux.kernel@googlegroups.com
Cc: Andreas Steinmetz <ast@domdv.de>,
linux-kernel@vger.kernel.org, hch@infradead.org,
torvalds@linux-foundation.org
Subject: Re: LIO - the broken iSCSI target implementation
Date: Fri, 18 Jan 2013 12:21:55 -0800 (PST) [thread overview]
Message-ID: <0a73688d-f466-4a96-89af-0dca4cb5ea8a@googlegroups.com> (raw)
In-Reply-To: <fa.xKOV9tOmjA6NPYEPagvZixrd/4w@ifi.uio.no>
Please don't start another "SCST Vs. LIO" holy war here. We all know why LIO belongs to Linux kernel and SCST does not.
On Friday, January 18, 2013 3:54:18 AM UTC+2, Vladislav Bolkhovitin wrote:
> Andreas Steinmetz, on 01/16/2013 08:19 PM wrote:
>
> > Thus, lio (http://www.linux-iscsi.org/) seemed to be the politically and
>
> > technically favoured solution.
>
>
>
> [...]
>
>
>
> > The fun part of it was that I finally ended up using SCST - which was
>
> > refrained from kernel inclusion for technical reasons beyond my
>
> > knowledge.
>
>
>
> No, it was purely political. There has never been any technical argument why LIO
>
> is better. And can not be.
>
>
>
> Thanks,
>
> Vlad
>
>
>
> --
>
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>
> the body of a message to majordomo@vger.kernel.org
>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2013-01-18 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.9LtpVDEImZxRAaqPOyWMlGOK4Ow@ifi.uio.no>
[not found] ` <fa.xKOV9tOmjA6NPYEPagvZixrd/4w@ifi.uio.no>
2013-01-18 20:21 ` promo [this message]
2013-01-19 15:36 ` Fubo Chen
2013-01-17 1:19 Andreas Steinmetz
2013-01-17 20:56 ` Nicholas A. Bellinger
2013-01-17 21:21 ` Nicholas A. Bellinger
2013-01-17 22:31 ` Andy Grover
2013-01-17 22:51 ` Linus Torvalds
2013-01-17 23:00 ` Nicholas A. Bellinger
2013-01-19 8:42 ` Ritesh Raj Sarraf
2013-01-18 1:53 ` 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=0a73688d-f466-4a96-89af-0dca4cb5ea8a@googlegroups.com \
--to=promo@starwindsoftware.com \
--cc=ast@domdv.de \
--cc=fa.linux.kernel@googlegroups.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®