From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: arjan@infradead.org, linux-scsi@vger.kernel.org,
iscsitarget-devel@lists.sourceforge.net
Subject: Re: [Iscsitarget-devel] Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 21:21:51 -0800 [thread overview]
Message-ID: <1109740911.3958.4.camel@mylaptop> (raw)
In-Reply-To: <20050302140413R.fujita.tomonori@lab.ntt.co.jp>
On Wed, 2005-03-02 at 14:04 +0900, FUJITA Tomonori wrote:
> From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Subject: [Iscsitarget-devel] Re: [ANNOUNCE] iSCSI enterprise target software
> Date: Tue, 01 Mar 2005 18:35:49 +0900
>
> > The last reason is that user-space cost like memory copy. With 1Gbs
> > Ethernet, is is not critical. However, with 10G, it is critical, I
> > expect. I've been setting up 10G experimental infrastructure to
> > evaluate iSCSI performance.
>
> If we try to build high-performance iSCSI target software on 10Gbs
> Ethernet, I think that we need to implement it in the kernel
> space, although this topic is still in the research stage.
>
> IICR, Intel provides open-source iSCSI target software, which uses
> mmap() in the user space, as you suggested. However, they chose a
> different approach to implement iSCSI target software for 10Gbs. They
> modified the Linux kernel TCP stack to fully integrate iSCSI
> functionality with it. It is still not clear how to get the best
> performance out of 10GBs Ethernet, however, it seems that using just
> the socket interface is not good enough. So I think that we need to
> control all the system-resources to do it.
>
> We've not optimized our code yet. The current code simply uses the
> socket interface, however, moving some functionality to the TCP stack
> can improve the performance, although I don't plan to modify theu TCP
> stack. A possible approach to do it is exploiting sk_data_ready().
www.open-iscsi.org project uses this technique on receiving path and
shows very nice performance numbers for Read operations comparable with
HW accelerators.
To add such a functionality to an existing project will probably require
total re-design.
Regards,
Dima
next prev parent reply other threads:[~2005-03-02 5:22 UTC|newest]
Thread overview: 32+ 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
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 [this message]
[not found] <20050301190140.97212.qmail@web30006.mail.mud.yahoo.com>
2005-03-01 19:29 ` Ming Zhang
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=1109740911.3958.4.camel@mylaptop \
--to=dmitry_yus@yahoo.com \
--cc=arjan@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--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 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.