linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@voltaire.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Joachim Fenkes <FENKES@de.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Christoph Raisch <raisch@de.ibm.com>,
	OF-General <general@lists.openfabrics.org>,
	Stefan Roscher <stefan.roscher@de.ibm.com>
Subject: Re: [ewg] Re: [PATCH] IB/ehca: Serialize HCA-related hCalls on POWER5
Date: Thu, 13 Dec 2007 10:30:56 +0200	[thread overview]
Message-ID: <4760EDC0.5020703@voltaire.com> (raw)
In-Reply-To: <adabq8v91co.fsf@cisco.com>

Roland Dreier wrote:
> I think the right fix for iSER would be to make iSER work even for
> devices that don't support FMRs.  For example cxgb3 doesn't implement
> FMRs so if anyone ever updates iSER to work on iWARP and not just IB,
> then this is something that has to be tackled anyway.  Then ehca could
> just get rid of the FMR support it has.

OK, The iSER design took into account the case of many initiators 
running on strong/modern machines talking to possibly lightweight 
embedded target for which the processing cost per I/O at the target side 
should be minimized, that is at most --one-- RDMA operation should be 
issued by the target to serve an I/O request.

For that end, iSER works with one descriptor (called stag in iWARP and 
rkey in IB) per I/O direction sent from the initiator to the target and 
hence can't work without some sort of FMR implementation.

The current implementation of the open iscsi initiator makes sure to 
issue commands in thread (sleepable) context, see iscsi_xmitworker and 
references to it in drivers/scsi/libiscsi.c , so this keeps ehca users 
safe for the time being.

Or.

  reply	other threads:[~2007-12-13  8:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 15:07 [PATCH] IB/ehca: Serialize HCA-related hCalls on POWER5 Joachim Fenkes
2007-12-06 15:48 ` Arnd Bergmann
2007-12-06 18:27   ` Roland Dreier
2007-12-07  9:58     ` Arnd Bergmann
2007-12-09 23:22       ` Roland Dreier
2007-12-10 17:41         ` Joachim Fenkes
2007-12-10 21:47           ` Roland Dreier
2007-12-11  8:38             ` Joachim Fenkes
2007-12-12 12:14               ` [ewg] " Or Gerlitz
2007-12-12 16:02                 ` Christoph Raisch
2007-12-12 19:09                 ` Roland Dreier
2007-12-13  8:30                   ` Or Gerlitz [this message]
2007-12-13 19:22                     ` [ofa-general] " Caitlin Bestler
2007-12-13 20:59                       ` Joachim Fenkes
2007-12-13 21:08                         ` Caitlin Bestler
2007-12-13 21:35                           ` Joachim Fenkes
2007-12-13 21:48                           ` [ofa-general] Re: [ewg] Re: [PATCH] IB/ehca: SerializeHCA-related " Sean Hefty
2007-12-07 16:25     ` [PATCH] IB/ehca: Serialize HCA-related " Joachim Fenkes

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=4760EDC0.5020703@voltaire.com \
    --to=ogerlitz@voltaire.com \
    --cc=FENKES@de.ibm.com \
    --cc=arnd@arndb.de \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=raisch@de.ibm.com \
    --cc=rdreier@cisco.com \
    --cc=stefan.roscher@de.ibm.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).