From: Ming Zhang <mingz@ele.uri.edu>
To: Vikas Aggarwal <vaggarwal2002@yahoo.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Tomonori Fujita <fujita.tomonori@lab.ntt.co.jp>,
arjan@infradead.org,
iet-dev <iscsitarget-devel@lists.sourceforge.net>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [Iscsitarget-devel] Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 14:29:25 -0500 [thread overview]
Message-ID: <1109705365.2878.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20050301190140.97212.qmail@web30006.mail.mud.yahoo.com>
On Tue, 2005-03-01 at 14:01, Vikas Aggarwal wrote:
> And If future IET be visioned as an Enterprise Class Array(Multiple
> Host-Side Adapters ie., FAs + Multiple Device Side Adapters ie., DAs),
> should better be in direct control of all the system-resources without
> being pushed out the kernel.
>
of course this is the reason why we use that name.
ming
> Bryan Henderson <hbryan@us.ibm.com> wrote:
> One thing that's implicit in your reasons for wanting to be in
> the kernel
> is that you've chosen to exploit the kernel's page cache. As a
> user of
> the page cache, you have more control from inside the kernel
> than from
> user space. The page cache was designed to be fundamentally
> invisible to
> user space.
>
> A pure user space implementation of an ISCSI target would use
> process
> virtual memory for a cache and manage it itself. It would
> access the
> storage with direct I/O. It looks to me like this is aimed at
> a
> single-application Linux system (the whole system is just an
> ISCSI
> target), which means there's not much need for a kernel to
> manage shared
> resources.
>
> --
> Bryan Henderson IBM Almaden Research Center
> San Jose CA Filesystems
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Pro duct Guide
> Read honest & candid reviews on hundreds of IT Products from
> real users.
> Discover which products truly live up to the hype. Start
> reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Iscsitarget-devel mailing list
> Iscsitarget-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel
>
> ______________________________________________________________________
> Do you Yahoo!?
> Read only the mail you want - Yahoo! Mail SpamGuard.
next parent reply other threads:[~2005-03-01 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050301190140.97212.qmail@web30006.mail.mud.yahoo.com>
2005-03-01 19:29 ` Ming Zhang [this message]
2005-03-01 7:19 [ANNOUNCE] iSCSI enterprise target software FUJITA Tomonori
2005-03-01 8:40 ` Arjan van de Ven
2005-03-01 9:35 ` FUJITA Tomonori
2005-03-01 9:46 ` Arjan van de Ven
2005-03-01 10:22 ` [Iscsitarget-devel] " FUJITA Tomonori
2005-03-01 10:33 ` Arjan van de Ven
2005-03-01 10:46 ` Arjan van de Ven
2005-03-01 11:23 ` FUJITA Tomonori
2005-03-01 10:48 ` Libor Vanek
2005-03-01 10:51 ` Arjan van de Ven
2005-03-02 5:04 ` FUJITA Tomonori
2005-03-02 5:21 ` Dmitry Yusupov
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=1109705365.2878.25.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=arjan@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hbryan@us.ibm.com \
--cc=iscsitarget-devel@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=vaggarwal2002@yahoo.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 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.