On Dec 13, 2007 12:30 AM, Or Gerlitz [EMAIL PROTECTED] wrote:
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,
[EMAIL PROTECTED] wrote on 13.12.2007 20:22:49:
On Dec 13, 2007 12:30 AM, Or Gerlitz [EMAIL PROTECTED] wrote:
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
Caitlin Bestler [EMAIL PROTECTED] wrote on 13.12.2007
22:08:34:
To clarify, an FMR Work Request is simply posted to the SendQ like
any other Work Request (of course the QP has to be privileged, or
it will complete in error). An SQ Post should never block.
This would require hardware support,
Or Gerlitz [EMAIL PROTECTED] wrote on 12.12.2007 13:14:25:
Joachim Fenkes wrote:
Roland Dreier [EMAIL PROTECTED] wrote on 10.12.2007 22:47:37:
It's an optional device feature, so this should be OK
(although the iSER driver currently seems to depend on a device
supporting FMRs, which is
Joachim Fenkes wrote:
Roland Dreier [EMAIL PROTECTED] wrote on 10.12.2007 22:47:37:
It's an optional device feature, so this should be OK
(although the iSER driver currently seems to depend on a device
supporting FMRs, which is probably going to be a problem with iWARP
support in the future
What is the fix you suggest, to add a device query that tells you for
which verbs the documentation does not apply? or enhance the code of the
map_phys_fmr verb within the ehca driver to return error if called
from non-sleepable context?
I think the right fix for iSER would be to
