From: Lloyd Brown <lloyd_brown-8Bzd4dk9+oo@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH][MINOR] mstflint/hca_self_test.ofed: Handle lspci output for ConnectX3 (on RHEL 6.2)
Date: Tue, 17 Jul 2012 10:11:30 -0600 [thread overview]
Message-ID: <50058EB2.8060600@byu.edu> (raw)
In-Reply-To: <1342103987-9341-1-git-send-email-lloyd_brown-8Bzd4dk9+oo@public.gmane.org>
Just wondering. Did I send this to the wrong place? Am I working off
the wrong repo? I expected such a simple patch to fly through, but I
haven't heard anything. If anyone can tell me what I did wrong, I'd be
happy to fix it.
Lloyd Brown
Systems Administrator
Fulton Supercomputing Lab
Brigham Young University
http://marylou.byu.edu
On 07/12/2012 08:39 AM, Lloyd Brown wrote:
> Not sure whether the difference is the hardware,
> or the OS revision, but the lspci output looks
> like this example, and wasn't being caught:
>
> 02:00.0 Network controller [0207]: Mellanox Technologies MT27500 Family [ConnectX-3]
>
> Signed-off-by: Lloyd Brown <lloyd_brown-8Bzd4dk9+oo@public.gmane.org>
> ---
> hca_self_test.ofed | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hca_self_test.ofed b/hca_self_test.ofed
> index c3e3f22..3c5360d 100755
> --- a/hca_self_test.ofed
> +++ b/hca_self_test.ofed
> @@ -110,7 +110,7 @@ MEM_CON_LSPCI_NAME="Memory controller"
> MEL_LSPCI_NAME_EXP="${HCA_LSPCI_NAME}|${VPI_LSPCI_NAME}|${NIC_LSPCI_NAME}"
>
> # HCA/PCI check
> -NUM_IB_DEV=`lspci 2> /dev/null | grep -E "(${MEL_LSPCI_NAME_EXP}): Mellanox Technolog" | wc -l`
> +NUM_IB_DEV=`lspci 2> /dev/null | grep -E "(${MEL_LSPCI_NAME_EXP})(\s\[[0-9]+\])?: Mellanox Technolog" | wc -l`
> NUM_MEM_CON=`lspci 2> /dev/null | grep "${MEM_CON_LSPCI_NAME}: Mellanox Technolog" | wc -l`
>
> let "NUM_HCAS=$NUM_IB_DEV + $NUM_MEM_CON"
> @@ -211,7 +211,7 @@ function get_curr_ca_pci_info () {
> loop_cnt=$1
>
> if [ "${g_lspci_was_ran}" == "" ]; then
> - lspci 2> /dev/null | grep -E "(${MEL_LSPCI_NAME_EXP}|${MEM_CON_LSPCI_NAME}): Mellanox Technolog" > ${G_LSPCI_OUTPUT_FILE}
> + lspci 2> /dev/null | grep -E "(${MEL_LSPCI_NAME_EXP}|${MEM_CON_LSPCI_NAME})(\s\[[0-9]+\])?: Mellanox Technolog" > ${G_LSPCI_OUTPUT_FILE}
> g_lspci_was_ran=1
> fi
> current_pci_info=$(cat ${G_LSPCI_OUTPUT_FILE} | head -$(expr $loop_cnt + 1) | tail -1)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-17 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 14:39 [PATCH][MINOR] mstflint/hca_self_test.ofed: Handle lspci output for ConnectX3 (on RHEL 6.2) Lloyd Brown
[not found] ` <1342103987-9341-1-git-send-email-lloyd_brown-8Bzd4dk9+oo@public.gmane.org>
2012-07-17 16:11 ` Lloyd Brown [this message]
[not found] ` <50058EB2.8060600-8Bzd4dk9+oo@public.gmane.org>
2012-07-17 17:02 ` Tziporet Koren
[not found] ` <CD250C48050CFB4D95E78C95F2FDDD6E86A2D3DC-fViJhHBwANKuSA5JZHE7gA@public.gmane.org>
2012-07-17 17:03 ` Lloyd Brown
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=50058EB2.8060600@byu.edu \
--to=lloyd_brown-8bzd4dk9+oo@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.