All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bolkhovitin <vst@vlnb.net>
To: FUJITA Tomonori <tomof@acm.org>
Cc: robert.w.love@intel.com, yi.zou@intel.com,
	christopher.leech@intel.com, vasu.dev@intel.com,
	linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: Open-FCoE on linux-scsi
Date: Tue, 08 Jan 2008 20:38:29 +0300	[thread overview]
Message-ID: <4783B515.1030001@vlnb.net> (raw)
In-Reply-To: <20080106103138Q.tomof@acm.org>

FUJITA Tomonori wrote:
>>Thus, I believe, that partial user space, partial kernel space approach 
>>for building SCSI targets is the move in the wrong direction, because it 
>>brings practically nothing, but costs a lot.
> 
> We have not discussed such topic. FCoE target can be implemented fully
> in user space if I understand correctly.

Really? FCoE target doesn't need an FC hardware target? And FCoE isn't 
sensitive to the packets forwarding latency?

For fully in-kernel approach it is possible to make the packets 
forwarding zero-copy in both directions FC<->Ethernet, which is 
practically impossible with user space. Modern memory has few GB/s 
throughput, so guess how much latency data copying will add on 10Gbps 
speed. Thus, I believe, if performance matters, FCoE should be in 
kernel, at least hot processing path, when management possibly done in 
user space as for open-iscsi. But user space/kernel separation should 
only be done if the additional user space/kernel interface won't 
complicate things too much.

Vlad

      reply	other threads:[~2008-01-08 17:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 23:40 Open-FCoE on linux-scsi Love, Robert W
2007-11-28  0:19 ` FUJITA Tomonori
2007-11-28  0:29   ` Love, Robert W
2007-12-28 19:11 ` FUJITA Tomonori
2007-12-31 16:34   ` Love, Robert W
2008-01-03 10:35     ` FUJITA Tomonori
2008-01-03 21:58       ` Love, Robert W
2008-01-04 11:45         ` Stefan Richter
2008-01-04 11:59           ` FUJITA Tomonori
2008-01-04 22:07             ` Dev, Vasu
2008-01-04 23:41               ` Stefan Richter
2008-01-05  0:09                 ` Stefan Richter
2008-01-05  0:21                   ` Stefan Richter
2008-01-05  8:28                     ` Christoph Hellwig
2008-01-15  1:18                   ` Love, Robert W
2008-01-15 22:18                     ` James Smart
2008-01-22 23:52                       ` Love, Robert W
2008-01-29  5:42                       ` Chris Leech
2008-02-01  1:53                         ` James Smart
2008-01-06  4:14                 ` FUJITA Tomonori
2008-01-06  4:27               ` FUJITA Tomonori
2008-01-04 13:47         ` FUJITA Tomonori
2008-01-04 20:19           ` Mike Christie
2008-01-05 18:33       ` Vladislav Bolkhovitin
2008-01-06  1:28         ` FUJITA Tomonori
2008-01-08 17:38           ` 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=4783B515.1030001@vlnb.net \
    --to=vst@vlnb.net \
    --cc=christopher.leech@intel.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=robert.w.love@intel.com \
    --cc=tomof@acm.org \
    --cc=vasu.dev@intel.com \
    --cc=yi.zou@intel.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.