linux-kernel - RE: [PATCH 3/3] net: define feature flags for FCoE offloads

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-prev] [day] [month] [year] [list]

Message-ID: <1DB50624F8348F48840F2E2CF6040A9D2F384148@orsmsx508.amr.corp.intel.com>
Date:	Thu, 20 Nov 2008 00:01:05 -0800
From:	"Zou, Yi" <yi.zou@...el.com>
To:	David Miller <davem@...emloft.net>
CC:	"jeff@...zik.org" <jeff@...zik.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 3/3] net: define feature flags for FCoE offloads

>From: David Miller [mailto:davem@...emloft.net]
>Sent: Wednesday, November 19, 2008 5:14 PM
>
>From: "Zou, Yi" <yi.zou@...el.com>
>Date: Wed, 19 Nov 2008 16:02:03 -0800
>
>> Thanks for reviewing the patch. I am hoping to make use of the
>> existing gso logic as much as possible for fcoe segmentation as
>> well, to hookup fcoe segmentation using ptype->gso_segment().
>
>There is no way for anyone to evaluate this usage and determine
>whether it makes sense or not until you post those patches.
Sure, allow me some time to clean up and repost patches following
this to RFC for what I think can be changed to make the existing
gso logic also work for fcoe.

Thanks for the comments.

-yi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/