On Thu, 2012-11-29 at 12:21 -0800, Roland Dreier wrote:
> On Mon, Nov 26, 2012 at 8:04 PM, David Dillow wrote:
> > We can push it through James's tree if need be, but Bart's code is
> > pretty self-contained, and going through the SCSI tree will introduce
> > merge dependencies. It'd be much easie
Just follow up on this:
For direct paththrough mode:
Problems was solved when I upgrade firmware with 2.9.1200,just as Albert's
suggestion as below:
http://marc.info/?t=13278909521&r=1&w=2
For SR-IOV mode
As I coundn't find a server with SR-IOV enabled.
I solved the problem with pci rescan,
Vipul,
Can you submit a bug in bugzilla for tracking? I will try to get to this
next couple of days.
-arlin
> -Original Message-
> From: Vipul Pandya [mailto:vi...@chelsio.com]
> Sent: Thursday, November 29, 2012 5:34 AM
> To: Davis, Arlin R
> Cc: Steve Wise; linux-rdma@vger.kernel.org;
On Mon, Nov 26, 2012 at 8:04 PM, David Dillow wrote:
> We can push it through James's tree if need be, but Bart's code is
> pretty self-contained, and going through the SCSI tree will introduce
> merge dependencies. It'd be much easier to push it all through the RDMA
> tree, especially if we want
thanks, applied for 3.8 with a stable cc.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2012-11-29 at 20:22 +0530, Vipul Pandya wrote:
> The T4 architecture is capable of filtering ingress packets at line rate
> using the rule in TCAM. If packet hits a rule in the TCAM then it can be
> either
> dropped or passed to the receive queues based on a rule settings.
>
> This patch
Signed-off-by: Jim Schutt
Signed-off-by: Hal Rosenstock
---
opensm/osm_torus.c | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/opensm/osm_torus.c b/opensm/osm_torus.c
index 43343c7..4d1bec7 100644
--- a/opensm/osm_torus.c
+++ b/opensm/osm_torus.c
@@ -7025,
> Was there progress on using rsocket under netperf or fork in general?
Fork support in rsockets is available now, and netperf should work. It's not
generic enough to handle any arbitrary call to fork, but will work if the app
does something like this:
listen()
s = accept()
fork(s)
> Do you
On Fri, Aug 24, 2012 at 8:35 PM, Hefty, Sean wrote:
>> I don't think those mmap()s should be an issue with fork they are
>> mapping adapter PCI space into userspace, but it should work across fork.
> makes sense
> Do you have any ideas on ways to identify what in the initialization paths
> m
It enables establishing active open connection using fw_ofld_connection work
request when cpl_act_open_rpl says TCAM full error which may be because
of LE hash collision. Current support is only for IPv4 active open connections.
Sets ntuple bits in active open requests. For T4 firmware greater tha
Retries active opens for INUSE errors.
Logs any active ofld_connect_wr error replies.
Sends ofld_connect_wr on same ctrlq. It needs to go on the same control txq as
regular CPL active/passive messages.
Retries on active open replies with EADDRINUSE.
Uses active open fw wr only if active filter
It establishes passive open connection through firmware work request. Passive
open connection will go through this path as now instead of listening server we
create a server filter which will redirect the incoming SYN packet to the
offload queue. After this driver tries to establish the connection
It supports establishing passive open connection through firmware filter work
request. Passive open connection will go through this path as now instead of
listening server we create a server filter which will redirect the incoming SYN
packet to the offload queue.
It divides filter region into regu
The T4 architecture is capable of filtering ingress packets at line rate
using the rule in TCAM. If packet hits a rule in the TCAM then it can be either
dropped or passed to the receive queues based on a rule settings.
This patch adds framework for managing filters and to use T4's filter
capabilit
This patch series fixes the LE hash collision issue in cxgb4 and RDMA/cxgb4
drivers in kernel.org.
If the hash functionality is enabled in T4 then tuple information of active and
passive offloaded connections are stored in DDR3 memory. LE (Lookup Engine)
implements the interface to search this tup
Hi Arlin,
This issue is happening because there is a port collision between
dapltest server port space and host TCP stack. The port collision
happens because rdma_bind_addr is getting called from the two different
places with different port arguments from dapltest. rdma_bind_addr is
getting called
16 matches
Mail list logo
