From: Bjorn Helgaas <bhelgaas@google.com>
To: Allen Hubbe <Allen.Hubbe@emc.com>
Cc: linux-ntb@googlegroups.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Jon Mason <jdmason@kudzu.us>,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [PATCH v3 03/18] NTB: Read peer info from local SPAD in transport
Date: Tue, 9 Jun 2015 11:24:52 -0500 [thread overview]
Message-ID: <20150609162452.GD23119@google.com> (raw)
In-Reply-To: <29c8beeb128ad2e86ee21dfebb5fb39056b47e93.1433838377.git.Allen.Hubbe@emc.com>
On Tue, Jun 09, 2015 at 05:44:30AM -0400, Allen Hubbe wrote:
> From: Dave Jiang <dave.jiang@intel.com>
>
> Importance: High
Looks like junk, maybe inadvertently copied from an email header?
> The transport was writing and then reading the peer spad, essentially
> reading what it just wrote instead of exchanging any information with
> the peer. The transport expects the peer values to be the same as the
> local values, so this issue was not obvious.
>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/ntb/ntb_transport.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> index 9faf1c6029af..d9538e911df6 100644
> --- a/drivers/ntb/ntb_transport.c
> +++ b/drivers/ntb/ntb_transport.c
> @@ -761,17 +761,17 @@ static void ntb_transport_link_work(struct work_struct *work)
> ntb_peer_spad_write(ndev, VERSION, NTB_TRANSPORT_VERSION);
>
> /* Query the remote side for its info */
> - val = ntb_peer_spad_read(ndev, VERSION);
> + val = ntb_spad_read(ndev, VERSION);
> dev_dbg(&pdev->dev, "Remote version = %d\n", val);
> if (val != NTB_TRANSPORT_VERSION)
> goto out;
>
> - val = ntb_peer_spad_read(ndev, NUM_QPS);
> + val = ntb_spad_read(ndev, NUM_QPS);
> dev_dbg(&pdev->dev, "Remote max number of qps = %d\n", val);
> if (val != nt->qp_count)
> goto out;
>
> - val = ntb_peer_spad_read(ndev, NUM_MWS);
> + val = ntb_spad_read(ndev, NUM_MWS);
> dev_dbg(&pdev->dev, "Remote number of mws = %d\n", val);
> if (val != nt->mw_count)
> goto out;
> @@ -779,10 +779,10 @@ static void ntb_transport_link_work(struct work_struct *work)
> for (i = 0; i < nt->mw_count; i++) {
> u64 val64;
>
> - val = ntb_peer_spad_read(ndev, MW0_SZ_HIGH + (i * 2));
> + val = ntb_spad_read(ndev, MW0_SZ_HIGH + (i * 2));
> val64 = (u64)val << 32;
>
> - val = ntb_peer_spad_read(ndev, MW0_SZ_LOW + (i * 2));
> + val = ntb_spad_read(ndev, MW0_SZ_LOW + (i * 2));
> val64 |= val;
>
> dev_dbg(&pdev->dev, "Remote MW%d size = %#llx\n", i, val64);
> --
> 2.4.0.rc0.43.gcf8a8c6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-09 16:24 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:44 [PATCH v3 00/18] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 01/18] NTB: Move files in preparation for NTB abstraction Allen Hubbe
2015-06-09 16:16 ` Bjorn Helgaas
2015-06-09 16:42 ` Hubbe, Allen
2015-06-09 16:42 ` Hubbe, Allen
2015-06-09 16:42 ` Hubbe, Allen
2015-06-09 9:44 ` [PATCH v3 02/18] NTB: Add NTB hardware abstraction layer Allen Hubbe
2015-06-09 16:23 ` Bjorn Helgaas
2015-06-09 16:43 ` Hubbe, Allen
2015-06-09 16:43 ` Hubbe, Allen
2015-06-09 16:43 ` Hubbe, Allen
2015-06-09 16:53 ` Bjorn Helgaas
2015-06-09 17:32 ` Hubbe, Allen
2015-06-09 17:32 ` Hubbe, Allen
2015-06-09 17:32 ` Hubbe, Allen
2015-06-09 9:44 ` [PATCH v3 03/18] NTB: Read peer info from local SPAD in transport Allen Hubbe
2015-06-09 16:24 ` Bjorn Helgaas [this message]
2015-06-09 9:44 ` [PATCH v3 04/18] NTB: Enable link for Intel root port mode in probe Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 05/18] NTB: Check the device ID to set errata flags Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 06/18] NTB: Differentiate transport link down messages Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 07/18] NTB: Do not advance transport RX on link down Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 08/18] NTB: Reset transport QP link stats on down Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 09/18] NTB: Add parameters for Intel SNB B2B addresses Allen Hubbe
2015-06-09 16:42 ` Bjorn Helgaas
2015-06-09 16:59 ` Hubbe, Allen
2015-06-09 16:59 ` Hubbe, Allen
2015-06-09 16:59 ` Hubbe, Allen
2015-06-09 9:44 ` [PATCH v3 10/18] NTB: Add ping pong test client Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 11/18] NTB: Add tool " Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 12/18] NTB: Rate limit ntb_qp_link_work Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 13/18] NTB: Use NUMA memory and DMA chan in transport Allen Hubbe
2015-06-09 16:43 ` Bjorn Helgaas
2015-06-09 9:44 ` [PATCH v3 14/18] NTB: Use NUMA memory in Intel driver Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 15/18] NTB: Improve performance with write combining Allen Hubbe
2015-06-09 16:46 ` Bjorn Helgaas
2015-06-09 9:44 ` [PATCH v3 16/18] NTB: Default to CPU memcpy for performance Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 17/18] NTB: Rename intel hw to proper platform names Allen Hubbe
2015-06-09 9:44 ` [PATCH v3 18/18] NTB: Increase transport MTU to 64k from 16k Allen Hubbe
2015-06-09 16:04 ` Bjorn Helgaas
2015-06-09 16:45 ` Jiang, Dave
2015-06-09 16:45 ` Jiang, Dave
2015-06-09 16:45 ` Jiang, Dave
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=20150609162452.GD23119@google.com \
--to=bhelgaas@google.com \
--cc=Allen.Hubbe@emc.com \
--cc=dave.jiang@intel.com \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.