From: Vladislav Bolkhovitin <vst@vlnb.net>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
scst-devel <scst-devel@lists.sourceforge.net>,
iscsitarget-devel@lists.sourceforge.net, stgt@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [ANNOUNCE]: Comparison of features sets between different SCSI targets (SCST, STGT, IET, LIO)
Date: Mon, 06 Apr 2009 21:57:56 +0400 [thread overview]
Message-ID: <49DA42A4.7060109@vlnb.net> (raw)
In-Reply-To: <c9a3e4540904060319l3c885641k1217fba468f1fcf8@mail.gmail.com>
ronnie sahlberg, on 04/06/2009 02:19 PM wrote:
> Why is AEN so important that it is worth 4 entries? SCST is the only
> target where this is supported.
About the related functionality see http://lkml.org/lkml/2009/3/26/290
> Has AEN not been replaced with sense codes nowadays anyway?
AEN, particularly, is one of the ways to deliver those sense codes
> Support for Asynchronous Event Notifications (AEN) + - - -
This is about the AEN infrastructure in the target's core
> AEN for devices added/removed + - - -
> AEN for devices resized + - - -
Those two are about ability to generate particular events
>
>
>
> Support for Asynchronous Event Notifications (AEN) + - - -
This is about support for AENs delivery by target driver.
>
>
>
>
>
> On Sun, Apr 5, 2009 at 5:56 AM, Vladislav Bolkhovitin <vst@vlnb.net
> <mailto:vst@vlnb.net>> wrote:
>
> Hi All,
>
> I set up http://scst.sourceforge.net/comparison.html page, which
> compares features of existing SCSI target subsystems for Linux. The
> comparison includes SCST, STGT, IET and LIO.
>
> I might be not fully correct somewhere, so, if you don't agree with
> me about some item(s) in the comparison table, please let me know
> and I will fix that.
>
> Vlad
> --
> To unsubscribe from this list: send the line "unsubscribe stgt" in
> the body of a message to majordomo@vger.kernel.org
> <mailto:majordomo@vger.kernel.org>
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2009-04-06 17:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 18:56 [ANNOUNCE]: Comparison of features sets between different SCSI targets (SCST, STGT, IET, LIO) Vladislav Bolkhovitin
2009-04-04 19:12 ` [Scst-devel] " Tomasz Chmielewski
2009-04-04 19:21 ` Vladislav Bolkhovitin
2009-04-06 9:44 ` Tomasz Chmielewski
2009-04-05 11:29 ` Bart Van Assche
2009-04-05 11:29 ` Bart Van Assche
2009-04-06 10:29 ` Tomasz Chmielewski
2009-04-06 10:40 ` Tomasz Chmielewski
2009-04-06 16:55 ` Vladislav Bolkhovitin
2009-04-06 18:27 ` Tomasz Chmielewski
2009-04-07 20:27 ` Bart Van Assche
2009-04-07 20:27 ` Bart Van Assche
2009-04-09 18:45 ` Vladislav Bolkhovitin
2009-04-14 11:07 ` Tomasz Chmielewski
2009-04-14 18:10 ` Vladislav Bolkhovitin
2009-04-06 19:01 ` Bart Van Assche
2009-04-06 19:01 ` Bart Van Assche
2009-04-06 19:05 ` Tomasz Chmielewski
[not found] ` <c9a3e4540904052019o3c89128eq52d9046fef7e2725@mail.gmail.com>
2009-04-06 7:32 ` Vladislav Bolkhovitin
[not found] ` <c9a3e4540904060057w75b5525an9c63486ed00ca9a5@mail.gmail.com>
2009-04-06 12:21 ` Vladislav Bolkhovitin
[not found] ` <c9a3e4540904060319l3c885641k1217fba468f1fcf8@mail.gmail.com>
2009-04-06 17:57 ` Vladislav Bolkhovitin [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=49DA42A4.7060109@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=scst-devel@lists.sourceforge.net \
--cc=stgt@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 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.