lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 3 Jun 2009 10:56:41 -0700
From:	"Zou, Yi" <yi.zou@...el.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"Leech, Christopher" <christopher.leech@...el.com>,
	"Dev, Vasu" <vasu.dev@...el.com>,
	"Love, Robert W" <robert.w.love@...el.com>,
	"Ma, Steve" <steve.ma@...el.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Subject: Question regarding protocol specific mtu for FCoE

Hi,
I am trying to figure out a way to support a different MTU for Fiber
Channel over Ethernet (FCoE), where it is preferred to have a baby jumbo
frame with MTU=2158 (14 bytes FCoE header + 24 bytes FC header + 2112
bytes max FC payload + 4 bytes FC CRC + 4 bytes FCoE trailer).

Similar to nedev->mtu being used everywhere for LAN traffic, I wonder if
it is desirable or feasible to add another protocol specific MTU (which
is my case is FCoE) to netdev so any eth driver supporting converged
traffic (e.g. LAN + FCoE) over netdev can make use of it.

Thanks.

Yi Zou

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ