netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: "Zou\, Yi" <yi.zou@intel.com>,
	"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-scsi\@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Leech\, Christopher" <christopher.leech@intel.com>, "Dev\,
	Vasu" <vasu.dev@intel.com>, "Love\,
	Robert W" <robert.w.love@intel.com>, "Ma\,
	Steve" <steve.ma@intel.com>, "Waskiewicz Jr\,
	Peter P" <peter.p.waskiewicz.jr@intel.com>, "Kirsher\,
	Jeffrey T" <jeffrey.t.kirsher@intel.com>
Subject: Re: Question regarding protocol specific mtu for FCoE
Date: Wed, 03 Jun 2009 16:27:25 -0700	[thread overview]
Message-ID: <adaiqjc99uq.fsf@cisco.com> (raw)
In-Reply-To: <4A26FB01.1020502@hp.com> (Rick Jones's message of "Wed, 03 Jun 2009 15:36:49 -0700")


 > Aren't all stations in the same broadcast domain "supposed" to have
 > the same MTU, at least down at L2? So, a station in the broadcast
 > domain just doing IP and a station in the broadcast domain doing
 > IP+FCoE "should" have the same MTU at the HW level right?
 > 
 > I could see where there would be lots of PMTU going-on if the
 > communications were to off-campus sites also had an FCoE upping their
 > MTU.  Otherwise, the MSS exchange at connection establishment is going
 > to preclude it right?  PMTU only "hits" when one has a so called
 > "dumb-bell" network which is "wider" at the ends than in the middle.

Yes, I think such dumb-bell networks would be pretty common (servers in
two different data centers with FCoE enabled, talking through an
old-school WAN with 1500 MTU).  And even if they're not as common I
think, we probably do want to have some way to handle this.

I'm probably not as up on old and/or obscure networking protocols, but
to me FCoE is the first time I've been forced to think about coexistence
of IP and non-IP protocols through the same netdev.

 - R.

      parent reply	other threads:[~2009-06-03 23:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 17:56 Question regarding protocol specific mtu for FCoE Zou, Yi
2009-06-03 18:03 ` Rick Jones
2009-06-03 19:16   ` Zou, Yi
2009-06-03 19:27     ` Ben Hutchings
2009-06-03 20:43       ` Zou, Yi
2009-06-03 20:57         ` Ben Hutchings
2009-06-03 22:22           ` Zou, Yi
2009-06-03 21:01     ` Rick Jones
2009-06-03 21:17       ` Waskiewicz Jr, Peter P
2009-06-03 21:21       ` Roland Dreier
2009-06-03 22:25         ` Zou, Yi
2009-06-03 22:36         ` Rick Jones
2009-06-03 23:00           ` Zou, Yi
2009-06-03 23:27           ` Roland Dreier [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=adaiqjc99uq.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=christopher.leech@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=rick.jones2@hp.com \
    --cc=robert.w.love@intel.com \
    --cc=steve.ma@intel.com \
    --cc=vasu.dev@intel.com \
    --cc=yi.zou@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).