public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
To: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: Moni Shoua <monis-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
	Vladimir Sokolovsky
	<vlad-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
	Eli Cohen <eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
	Linux RDMA list
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: are IB port counters functioning over --IB-- with the RDMAoE patch set?
Date: Mon, 07 Jun 2010 16:29:48 +0300	[thread overview]
Message-ID: <4C0CF44C.5030702@Voltaire.com> (raw)
In-Reply-To: <AANLkTin5E1BHRr4pwWnueo0zqhn_3VyQThRVSFTiAZad-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Eli Cohen wrote:
> counter should work as regular in upstream kernel patches for IB link layer. 

okay good, can you validate that? basically, I can set some time to clone Roland's tree
and use the iboe branch as a basis for testing that the IB stack is live and kicking as it used to be before the patches. I just need an updated copy of the rest of the patch set (Roland has three patches so far) for that end. Over the review process there were bunch of comments but no new posting, how are you planning to proceed in the review/merge process?

> for IBoE, they will not work since the SMA does not support them
> I have patches that allow to show counters using sysfs 

I am not with you. The counters are read using a MAD sent to the firmware PMA (QP #1), 
this applies for both perfquery and sysfs, isn't it? 

Or.
--
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

  parent reply	other threads:[~2010-06-07 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  9:04 are IB port counters functioning over --IB-- with the RDMAoE patch set? Or Gerlitz
     [not found] ` <4BFE35B7.80009-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-06-03 11:49   ` Or Gerlitz
     [not found]     ` <4C0796C1.1040106-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-06-03 12:06       ` Moni Shoua
     [not found]         ` <7E95F01E94AB484F83061FCFA35B39F854FBAA-QfUkFaTmzUSUvQqKE/ONIwC/G2K4zDHf@public.gmane.org>
2010-06-03 13:33           ` Or Gerlitz
     [not found]             ` <4C07AF24.6000006-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-06-07  9:40               ` Eli Cohen
     [not found]                 ` <AANLkTin5E1BHRr4pwWnueo0zqhn_3VyQThRVSFTiAZad-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-07 13:29                   ` Or Gerlitz [this message]
     [not found]                     ` <4C0CF44C.5030702-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-06-07 13:45                       ` Eli Cohen
     [not found]                         ` <AANLkTinT9KSwT16drtXPC2kfr6fF4NJJMBhF6ga3jpMp-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-07 14:28                           ` Or Gerlitz

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=4C0CF44C.5030702@Voltaire.com \
    --to=ogerlitz-hkgkho2ms0fwk0htik3j/w@public.gmane.org \
    --cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=monis-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=vlad-VPRAkNaXOzVS1MOuV/RT9w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox