public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Aleksey Senin <aleksey-192fA4vuk7xBDLzU/O5InQ@public.gmane.org>,
	Yevgeny Petrilin
	<yevgenyp-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Cc: Jack Morgenstein
	<jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
	alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH V2] mlx4: Protocol distinction
Date: Thu, 2 Dec 2010 09:26:56 +0200	[thread overview]
Message-ID: <4CF74A40.5000608@voltaire.com> (raw)
In-Reply-To: <AANLkTikBwo5sOo0-uDz28o_eqqMk4t=ME-TxeLZzO0+F-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 12/2/2010 8:53 AM, Aleksey Senin wrote:
> I don't think that this specific change should check firmware version,
> because it not dealing with hardware directly and it should work with
> older firmware too.

So the modified code works with older firmware, good news, Yevgeny, does 
this apply also to UC/MC steering patches which Tziporet mentioned recently?

> Its restriction, that now it will support 2^30 members for QP instead of 2^32.

I don't understand what "members for QP" means. And anyway, I don't 
think there's something in the HCA which can be allocated in the order 
of Gigs (billions, except maybe for bandwidth...) typically it goes up 
to Megs (millions). Also, as said here and elsewhere couple of times, 
bottom posting is very much easier and fun to work with for open-source 
development, if you want to learn a bit more on that, take a look @ 
http://www.caliburn.nl/topposting.html


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-12-02  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 16:13 [PATCH V2] mlx4: Protocol distinction Aleksey Senin
     [not found] ` <4CF67444.4080001-192fA4vuk7xBDLzU/O5InQ@public.gmane.org>
2010-12-01 17:51   ` Roland Dreier
     [not found]     ` <adahbexnzyt.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2010-12-01 18:19       ` Aleksey Senin
2010-12-01 21:12   ` Or Gerlitz
     [not found]     ` <AANLkTinwpuUis2Xj_U3PNSmZcM3LFr+A9V3JXanvH2Jr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-02  6:53       ` Aleksey Senin
     [not found]         ` <AANLkTikBwo5sOo0-uDz28o_eqqMk4t=ME-TxeLZzO0+F-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-12-02  7:26           ` Or Gerlitz [this message]
     [not found]             ` <4CF74A40.5000608-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-12-02  7:45               ` Yevgeny Petrilin

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=4CF74A40.5000608@voltaire.com \
    --to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=aleksey-192fA4vuk7xBDLzU/O5InQ@public.gmane.org \
    --cc=alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
    --cc=yevgenyp-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