netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Yusupov <dmitry_yus@yahoo.com>
To: "open-iscsi@googlegroups.com" <open-iscsi@googlegroups.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	mpm@selenic.com, andrea@suse.de, michaelc@cs.wisc.edu,
	James.Bottomley@HansenPartnership.com,
	ksummit-2005-discuss@thunk.org, netdev@oss.sgi.com
Subject: Re: Linux support for RDMA (was: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics)
Date: Sun, 03 Apr 2005 17:56:11 -0700	[thread overview]
Message-ID: <1112576171.4227.5.camel@mylaptop> (raw)
In-Reply-To: <67D69596DDF0C2448DB0F0547D0F947E01781F2E@yogi.asicdesigners.com>

On Sat, 2005-04-02 at 11:07 -0800, Asgeir Eiriksson wrote:
> Dmitry

> The CPU cycles is only at most half of the story with the other half
> being the memory sub-system BW.
> 
> So the validity of your observation depends on the BW we're talking
> about, i.e. if the client is using a fraction of 10Gbps for RDMA (or
> DDP, e.g. iSCSI DDP), yes then that fraction amounts to a fraction of
> the memory sub-system total BW so we don't much care about the extra
> copy.
> 
> The situation is different if the client wants something close to 10Gbps
> (already have such client applications), because today 10Gbps is still a
> big chunk of the overall memory BW so you really care about eliminating
> that copy via DDP.

I do not get your concern with memory BW. With good AMD box V40Z(SUN)
you can get 5.3GBytes/sec. Even with 10Gbps full speed you have 80%
left. PCI-X BUS BW is bigger concern...

> 'Asgeir
> 
> > -----Original Message-----
> > From: netdev-bounce@oss.sgi.com [mailto:netdev-bounce@oss.sgi.com] On
> > Behalf Of Dmitry Yusupov
> > Sent: Saturday, April 02, 2005 10:09 AM
> > To: open-iscsi@googlegroups.com
> > Cc: David S. Miller; mpm@selenic.com; andrea@suse.de;
> > michaelc@cs.wisc.edu; James.Bottomley@HansenPartnership.com;
> ksummit-2005-
> > discuss@thunk.org; netdev@oss.sgi.com
> > Subject: Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit
> > ProposedTopics
> > 
> > On Mon, 2005-03-28 at 17:32 -0500, Benjamin LaHaise wrote:
> > > On Mon, Mar 28, 2005 at 12:48:56PM -0800, Dmitry Yusupov wrote:
> > > > If you have plans to start new project such as SoftRDMA than yes.
> lets
> > > > discuss it since set of problems will be similar to what we've got
> > with
> > > > software iSCSI Initiators.
> > >
> > > I'm somewhat interested in seeing a SoftRDMA project get off the
> ground.
> > > At least the NatSemi 83820 gige MAC is able to provide early-rx
> > interrupts
> > > that allow one to get an rx interrupt before the full payload has
> > arrived
> > > making it possible to write out a new rx descriptor to place the
> payload
> > > wherever it is ultimately desired.  It would be fun to work on if
> not
> > the
> > > most performant RDMA implementation.
> > 
> > I see a lot of skepticism around early-rx interrupt schema. It might
> > work for gige, but i'm not sure if it will fit into 10g.
> > 
> > What RDMA gives us is zero-copy on receive and new networking api
> which
> > has a potential to be HW accelerated. SoftRDMA will never avoid
> copying
> > on receive. But benefit for SoftRDMA would be its availability on
> client
> > sides. It is free and it could be easily deployed. Soon Intel & Co
> will
> > give us 2,4,8... multi-core CPUs for around 200$ :), So, who cares if
> > one of those cores will do receive side copying?
> > 
> 
> 

  parent reply	other threads:[~2005-04-04  0:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-02 19:07 [Ksummit-2005-discuss] Summary of 2005 Kernel Summit ProposedTopics Asgeir Eiriksson
2005-04-02 19:14 ` Ming Zhang
2005-04-04  0:56 ` Dmitry Yusupov [this message]
2005-04-04  6:34   ` Linux support for RDMA (was: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics) Grant Grundler
2005-04-04  7:10     ` David S. Miller
2005-04-04 12:58       ` Ming Zhang
2005-04-04 16:31       ` Grant Grundler
2005-04-04 12:56     ` Ming Zhang
2005-04-04 16:54     ` Dmitry Yusupov
2005-04-04 19:11       ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05 22:19 jaganav
2005-04-02  7:29 jaganav
2005-04-02 18:27 ` Matthew Wilcox
2005-04-03  1:26 ` Grant Grundler
2005-04-05 15:04 ` Rik van Riel
2005-04-01  2:13 jaganav
2005-04-01 23:43 ` Stephen Hemminger
2005-04-02  1:37   ` jaganav
2005-04-02  5:27     ` Greg KH
2005-04-02  6:02       ` Greg KH
2005-04-02 15:01         ` Andrea Arcangeli
2005-04-04 16:50     ` Stephen Hemminger
     [not found] <4241D106.8050302@cs.wisc.edu>
     [not found] ` <20050324101622S.fujita.tomonori@lab.ntt.co.jp>
     [not found]   ` <1111628393.1548.307.camel@beastie>
     [not found]     ` <20050324113312W.fujita.tomonori@lab.ntt.co.jp>
     [not found]       ` <1111633846.1548.318.camel@beastie>
     [not found]         ` <20050324215922.GT14202@opteron.random>
     [not found]           ` <424346FE.20704@cs.wisc.edu>
     [not found]             ` <20050324233921.GZ14202@opteron.random>
     [not found]               ` <20050325034341.GV32638@waste.org>
     [not found]                 ` <20050327035149.GD4053@g5.random>
2005-03-27  5:48                   ` [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics Matt Mackall
2005-03-27  6:33                     ` Dmitry Yusupov
2005-03-27  6:46                       ` David S. Miller
2005-03-28 19:45                         ` Roland Dreier
     [not found]                           ` <1112042936.5088.22.camel@beastie>
2005-03-28 22:32                             ` Benjamin LaHaise
2005-03-29  3:19                               ` Linux support for RDMA (was: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics) Roland Dreier
2005-03-30 16:00                                 ` Benjamin LaHaise
2005-03-29  3:14                             ` Roland Dreier

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=1112576171.4227.5.camel@mylaptop \
    --to=dmitry_yus@yahoo.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrea@suse.de \
    --cc=davem@davemloft.net \
    --cc=ksummit-2005-discuss@thunk.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=mpm@selenic.com \
    --cc=netdev@oss.sgi.com \
    --cc=open-iscsi@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).