public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	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: Wed, 02 Mar 2005 14:34:00 -0500	[thread overview]
Message-ID: <1109792040.2878.102.camel@localhost.localdomain> (raw)
In-Reply-To: <OF28B4EEEA.0271C53B-ON85256FB8.0064150B-88256FB8.00646550@us.ibm.com>

On Wed, 2005-03-02 at 13:20, Bryan Henderson wrote:
> >u are talking about application aware caching/prefetching stuff. but i
> >prefer to modifying kernel page cache a little bit while make use of
> >most of the code there.
> 
> That's a powerful argument for using the page cache, and further, for 
> using it from within the kernel.  I once started a project to port a 
> particular filesystem driver from the kernel to user space.  It was to be 
> used in a Linux system whose sole purpose was to export one filesystem via 
> NFS.  I was looking for engineering ease.  Everything about porting the 
> driver to user space was almost trivial except for duplicating the page 
> cache, and that was enough work to call into question the whole strategy 
> (I never went far enough to actually make a decision).
> 
i tried several time before on implementing own cache structures in user
space/ kernel space. every time i think i can do it better than before.
but frankly, there are always corner cases that make it performs poor.


> But I'm sure there are cases where the tradeoff works.
yes. i am sure about this as well.

> 
> --
> Bryan Henderson                               San Jose California
> IBM Almaden Research Center                   Filesystems


  reply	other threads:[~2005-03-02 19:34 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
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 [this message]
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=1109792040.2878.102.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 \
    /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