From: Ming Zhang <mingz@ele.uri.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Bryan Henderson <hbryan@us.ibm.com>,
Tomonori Fujita <fujita.tomonori@lab.ntt.co.jp>,
iet-dev <iscsitarget-devel@lists.sourceforge.net>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 14:14:47 -0500 [thread overview]
Message-ID: <1109704486.2878.23.camel@localhost.localdomain> (raw)
In-Reply-To: <4224BC17.7000103@pobox.com>
On Tue, 2005-03-01 at 14:01, Jeff Garzik wrote:
> Ming Zhang wrote:
> > On Tue, 2005-03-01 at 13:37, Arjan van de Ven wrote:
> >
> >>On Tue, 2005-03-01 at 10:24 -0800, Bryan Henderson 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.
> >>
> >>why would it use direct I/O ? Direct I/O would be really stupid for such
> >>a thing to use since that means there's no caching going on *at all*.
> >>
> >
> > what Bryan suggest is a privately owned and managed user space cache. so
> > for that disk write should be real write-through.
> >
> > it is hard to beat linux kernel cache performance though.
>
> A privately managed user space cache uses Linux kernel cache.
what i mean is private cache algorithms. for example, windows request
are not page size aligned so some bitmap based cache algorithms might be
useful.
>
> As does mmap/sendfile...
>
> Jeff
>
next prev parent reply other threads:[~2005-03-01 19:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
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-01 18:24 ` Bryan Henderson
2005-03-01 18:37 ` Arjan van de Ven
2005-03-01 18:48 ` Ming Zhang
2005-03-01 19:01 ` Jeff Garzik
2005-03-01 19:14 ` Ming Zhang [this message]
2005-03-01 21:04 ` Bryan Henderson
2005-03-01 21:15 ` Ming Zhang
2005-03-02 18:20 ` Bryan Henderson
2005-03-02 19:34 ` Ming Zhang
2005-03-01 21:16 ` Arjan van de Ven
2005-03-02 18:27 ` Bryan Henderson
2005-03-02 3:30 ` FUJITA Tomonori
2005-03-01 20:38 ` Andi Kleen
2005-03-01 20:49 ` Ming Zhang
2005-03-01 22:19 ` Christoph Hellwig
2005-03-01 20:53 ` Bryan Henderson
2005-03-01 20:58 ` Arjan van de Ven
2005-03-02 10:47 ` Vladislav Bolkhovitin
2005-03-02 18:39 ` Bryan Henderson
2005-03-02 5:04 ` [Iscsitarget-devel] " 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=1109704486.2878.23.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=jgarzik@pobox.com \
--cc=linux-scsi@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