summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorJon Mason <jon.mason@intel.com>2013-02-01 15:34:35 -0700
committerJon Mason <jon.mason@intel.com>2013-05-15 10:57:51 -0700
commit90f9e934647e652a69396e18c779215a493271cf (patch)
tree73fd87122d939e395d7d56d4b41e58840e57eca7 /drivers
parentb77b2637b39ecc380bb08992380d7d48452b0872 (diff)
downloadlinux-90f9e934647e652a69396e18c779215a493271cf.tar.gz
linux-90f9e934647e652a69396e18c779215a493271cf.tar.bz2
linux-90f9e934647e652a69396e18c779215a493271cf.zip
NTB: reset tx_index on link toggle
If the NTB link toggles, the driver could stop receiving due to the tx_index not being set to 0 on the transmitting size on a link-up event. This is due to the driver expecting the incoming data to start at the beginning of the receive buffer and not at a random place. Signed-off-by: Jon Mason <jon.mason@intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/ntb/ntb_transport.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
index be416d6850f0..73a000ed7a9f 100644
--- a/drivers/ntb/ntb_transport.c
+++ b/drivers/ntb/ntb_transport.c
@@ -505,6 +505,7 @@ static void ntb_transport_setup_qp_mw(struct ntb_transport *nt,
qp->rx_pkts = 0;
qp->tx_pkts = 0;
+ qp->tx_index = 0;
}
static void ntb_free_mw(struct ntb_transport *nt, int num_mw)
@@ -819,7 +820,6 @@ static void ntb_transport_init_queue(struct ntb_transport *nt,
qp->tx_mw = qp->rx_info + 1;
qp->tx_max_frame = min(transport_mtu, tx_size);
qp->tx_max_entry = tx_size / qp->tx_max_frame;
- qp->tx_index = 0;
if (nt->debugfs_dir) {
char debugfs_name[4];