From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Liran Liss <liranl-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Or Gerlitz <or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Yevgeny Petrilin
<yevgenyp-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Richard Frank
<richard.frank-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Paul Grun
<pgrun-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
Subject: Re: RDMAoE / lossless Ethernet (ewg: SC'09 BOF - Meeting notes)
Date: Thu, 24 Dec 2009 14:49:24 +0200 [thread overview]
Message-ID: <4B336354.2060305@voltaire.com> (raw)
In-Reply-To: <2ED289D4E09FBD4D92D911E869B97FDD0222EFDF-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org>
Liran Liss wrote:
> I second...
>
fair-enough, so now (A) everyone agrees that DCB is good for IBoE and
(B) mlx4 supports pfc, any reason not to push the pfc patches into the
kernel and have mlx4_en comply with the mainline dcbnl code?
> The only way an end-node can cause congestion is if its internal buses don't match the IB link's BW, but this is unrelated to (lack of) transport-level flow control.
>
thanks for clarifying this
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
next prev parent reply other threads:[~2009-12-24 12:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ED289D4E09FBD4D92D911E869B97FDD01AF10F2@mtlexch01.mtl.com>
[not found] ` <2ED289D4E09FBD4D92D911E869B97FDD01AF10F2-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org>
2009-12-23 8:09 ` RDMAoE / lossless Ethernet (ewg: SC'09 BOF - Meeting notes) Or Gerlitz
[not found] ` <4B31D048.5040001-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2009-12-23 15:52 ` Roland Dreier
[not found] ` <adahbrh1yd0.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-12-23 22:12 ` Or Gerlitz
[not found] ` <15ddcffd0912231412y8f6724fh5a7036f30117189e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-24 0:46 ` Roland Dreier
[not found] ` <adad42519n5.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-12-24 8:40 ` Liran Liss
[not found] ` <2ED289D4E09FBD4D92D911E869B97FDD0222EFDF-ia22CT07NJfiMCgWhms8HQC/G2K4zDHf@public.gmane.org>
2009-12-24 12:49 ` Or Gerlitz [this message]
2009-12-24 12:25 ` Or Gerlitz
[not found] ` <4B335DCD.4080201-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2009-12-24 15:59 ` Roland Dreier
[not found] ` <001101ca8411$68244b80$386ce280$@com>
2009-12-23 22:17 ` Or Gerlitz
[not found] ` <15ddcffd0912231417h6e47db36ledbdb2ad6cc66c0e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-12-24 0:09 ` Paul Grun
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=4B336354.2060305@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liranl-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pgrun-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=richard.frank-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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