From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Christoph Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
Cc: Alekseys Senin <alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Moni Shoua <monis-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] Make multicast and path record queue flexible.
Date: Wed, 6 Oct 2010 11:34:49 -0600 [thread overview]
Message-ID: <20101006173449.GJ24268@obsidianresearch.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010061114590.31538-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
On Wed, Oct 06, 2010 at 11:16:59AM -0500, Christoph Lameter wrote:
> > Relating to broadcast, I don't think that this is a good solution it
> > will bring unwarranted load, specially in the case if no MLID received.
> > The way of adding delay before we start to send packages, seems to me
> > better.
>
> Broadcast is a temporary solution and it only occurs with in an IB
> partition. It would be a problem if one host suddenly starts sending
> at full line speed. Maybe have that configurable?
Right, and keep in mind that sending a packet with the broadcast MLID
and group-specific MGID will still result in the HCA's filtering based
on MGID. Personally, I'm not concerned about flooding - this is how
things work in ethernet - any sane app will need some way to cope with
that.
Jason
--
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
prev parent reply other threads:[~2010-10-06 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 16:07 [PATCH] Make multicast and path record queue flexible Aleksey Senin
[not found] ` <4CAB4D49.9090107-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-10-05 16:28 ` Jason Gunthorpe
[not found] ` <20101005162833.GC5967-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-05 19:12 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010051410370.7065-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-05 19:54 ` Jason Gunthorpe
[not found] ` <20101005195428.GB24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-05 20:02 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010051500330.8786-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-05 20:21 ` Jason Gunthorpe
[not found] ` <20101005202121.GC24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-05 20:43 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010051535480.10603-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-05 20:55 ` Jason Gunthorpe
[not found] ` <20101005205545.GF24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-05 21:12 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010051600190.10603-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-05 21:28 ` Jason Gunthorpe
[not found] ` <20101005212826.GG24268-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-05 21:34 ` Christoph Lameter
2010-10-12 16:29 ` Alekseys Senin
[not found] ` <1286900993.31931.4.camel-uOVkuFIEnOODI2cvxHXf6UEOCMrvLtNR@public.gmane.org>
2010-10-12 20:47 ` Jason Gunthorpe
2010-10-05 19:18 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010051415100.7065-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-06 15:57 ` Alekseys Senin
[not found] ` <1286380676.31487.1.camel-uOVkuFIEnOODI2cvxHXf6UEOCMrvLtNR@public.gmane.org>
2010-10-06 16:16 ` Christoph Lameter
[not found] ` <alpine.DEB.2.00.1010061114590.31538-sBS69tsa9Uj/9pzu0YdTqQ@public.gmane.org>
2010-10-06 17:34 ` Jason Gunthorpe [this message]
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=20101006173449.GJ24268@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=alekseys-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=rolandd-FYB4Gu1CFyUAvxtiuMwx3w@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.