From: Ben Hutchings <bhutchings@solarflare.com>
To: "Zou, Yi" <yi.zou@intel.com>
Cc: Rick Jones <rick.jones2@hp.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 20:27:25 +0100 [thread overview]
Message-ID: <1244057245.3191.17.camel@achroite> (raw)
In-Reply-To: <7C88852EF6F99F4EB538472FCFEBE2223A7E6FBD@orsmsx509.amr.corp.intel.com>
On Wed, 2009-06-03 at 12:16 -0700, Zou, Yi wrote:
[...]
> FCoE is on L2 layer, no path specific MTU, everything goes out as
> whatever mtu known to the nic. Since the nic is expected to be used for
> converged traffic involving multiple traffic types, e.g. LAN, FCoE, I
> was wondering if it makes sense to have the additional MTU. Essentially,
> the nic driver will be able to setup via netdev for different MTUs for
> converged traffic.
Wouldn't you use separate VLANs for FCoE and other traffic? So maybe we
should allow for per-VLAN rather than per-protocol MTU.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2009-06-03 19: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 [this message]
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
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=1244057245.3191.17.camel@achroite \
--to=bhutchings@solarflare.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).