[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080813.190905.31828583.davem@davemloft.net>
Date: Wed, 13 Aug 2008 19:09:05 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: tom@...ngridcomputing.com
Cc: rdreier@...co.com, rick.jones2@...com, jgarzik@...ox.com,
swise@...ngridcomputing.com, divy@...lsio.com, kxie@...lsio.com,
netdev@...r.kernel.org, open-iscsi@...glegroups.com,
michaelc@...wisc.edu, daisyc@...ibm.com, wenxiong@...ibm.com,
bhua@...ibm.com, dm@...lsio.com, leedom@...lsio.com,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH 1/1] cxgb3i: cxgb3 iSCSI initiator
From: Tom Tucker <tom@...ngridcomputing.com>
Date: Wed, 13 Aug 2008 20:26:51 -0500
> Is there any chance your could discuss exactly how a stateless adapter
> can determine if a network segment
> is in-order, next expected, minus productive ack, paws compliant, etc...
> without TCP state?
If you're getting packets out of order, data placement optimizations
are the least of your concerns.
In fact this is exactly where we want all of the advanced loss
handling algorithms of the Linux TCP stack to get engaged.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists