|Publication number||US6959007 B1|
|Application number||US 09/888,902|
|Publication date||Oct 25, 2005|
|Filing date||Jun 25, 2001|
|Priority date||Mar 1, 2001|
|Publication number||09888902, 888902, US 6959007 B1, US 6959007B1, US-B1-6959007, US6959007 B1, US6959007B1|
|Inventors||Danny C. Vogel, Clinton P. Seeman|
|Original Assignee||Lsi Logic Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (2), Referenced by (89), Classifications (14), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims the benefit of U.S. Provisional Application No. 60/273,072, filed Mar. 1, 2001, and is hereby incorporated by reference in its entirety.
The present invention relates to network protocol stack processing generally and, more particularly, to a method and/or architecture for a high speed TCP/IP/UDP protocol stack in silicon that may be used in internet Fiber Channel (iFC) and internet SCSI (iSCSI) designs.
Internet SCSI and iFC are protocols for encapsulating (establishing and transporting) SCSI and FC commands across an internet protocol (IP) network instead of a direct SCSI or FC compatible cable. By using iSCSI or iFC, storage management software that was originally written for SCSI or FC can be used to make a remote disk or tape drive on a network operate like a local disk. The network can be a local area network such as ethernet or even the internet.
Internet SCSI (iSCSI) and iFC target rates of 1 Gbps and 10 Gbps. Current TCP/IP designs to support iSCSI and iFC can be slow and power hungry. Conventional designs use firmware based TCP/IP stacks, with additional software for iSCSI/iFC stacks, and additional Ethernet MAC hardware components. The firmware based TCP/IP stacks are executed on expensive network or high end processors. The conventional designs can be expensive, require a large chip count, require high power, and provide inadequate bandwidth (i.e., not scalable to 10 Gbps).
The present invention concerns an apparatus comprising a media access controller (MAC), a configurable packet switch, and a network protocol stack in silicon. The network protocol stack may be configured to couple the media access controller to the configurable packet switch.
The objects, features and advantages of the present invention include providing a method and/or architecture for high speed TCP/IP/UDP protocol stack in silicon that may (i) be used in internet Fiber Channel (iFC) and internet SCSI (iSCSI) designs, (ii) provide bandwidth support for 1 Gbps and 10 Gbps without an expensive network or high end processor, (iii) easily support and redirect control and data flows, (iv) provide support for security, (v) included ethernet MAC functionality, (vi) provide support for TCP/IP/UDP, as well as ease of extension to external SCTP protocols, and/or (vii) provide ease of extension by means of an external bus (e.g., RIO, PCI, PCI-x, etc.).
These and other objects, features and advantages of the present invention will be apparent from the following detailed description and the appended claims and drawings in which:
The system 100 may have an interface 110 that may be connected to a host 112, an interface 114 that may be connected to a memory block 116, and an interface 118 that may be connected to an external processor 120. The interface 114 may be implemented, in one example, as a double data rate (DDR) interface. The memory 116 may be implemented as RAM, SDRAM or any other type of memory appropriate to meeting the design criteria of a particular application. The processor 120 may be implemented, in one example, as a security processing chip. In one example, the processor 120 may be configured to implement an SSL and/or IPSec security protocol. The host 112 may be implemented as a processor (e.g., a Power PC) to implement an iSCSI control stack. The host 112 may be configured to control and manage the system 100. The host 112 may be further configured to process in-band control blocks (e.g., SMTP management).
In one example, the circuit 130 may be implemented as a 100/1G/10G ethernet MAC. The circuit 130 may be configured to provide an external GMII and/or XGMII interface that may be coupled to the physical layer device 102 via the bus 104. The circuit 130 may be configured to run at any of a number of network speeds (e.g., 100 Mbps, 1 Gbps, 10 Gbps, etc.).
The circuit 132 may comprised of a buffer controller, a memory block, and a data switch. The memory block may be utilized to implement a FIFO memory to decouple the MAC 130 from the remainder of the circuit (e.g., in terms of data movement). The buffer controller may be configured to implement the normal aspects of a FIFO, as well as those aspects unique to Ethernet. For example, the buffer controller may be configured to retain initial data octets of a transmitted packet in the FIFO until after an early collision threshold has been passed, in order to allow for automatic retransmission, in accordance with the Ethernet standard. The data switch block functionality may be split between the circuit 132 and the circuit 136. The data switch block in the circuit 132 may be configured to detect encrypted blocks (e.g., IPSec), or blocks to be encrypted utilizing IPSec, and direct the blocks to the external IPSec/SSL co-processing chip 120 via the interface (port) 118. Within the circuit 136, the data switch block may be configured to detect blocks to be encrypted (e.g., utilizing SSL), or that are encrypted utilizing SSL, and direct the blocks to the external IPSec/SSL co-processing chip 120 via the interface 118.
The circuit 134 may be implemented, in one example, as a TCP/IP stack in silicon. The circuit 134 may be configured to support IP, TCP, UDP, and other transport layer type protocols. The circuit 134 may be configured to run the IP protocol and TCP, UDP and/or other protocols simultaneously at greater than 1 Gbps rate. The circuit 134 may be coupled to the memory 116 via the interface 114. The circuit 134 may be implemented, in one example, similarly to a circuit described in a co-pending patent application U.S. Ser. No. 09/888,866 which is hereby incorporated by reference in its entirety.
The circuit 136 may be implemented as a configurable packet switch. The circuit 136 may be configured to switch packets (e.g., SCSI packets) to either the circuit 106 (e.g., via the bus 108) or to an external processor for management and control processing. The circuits 130, 132, 134, and 136 may be controlled and managed by the host 112 via the interface 110.
The circuit 142 may be configured for implementing normal IP layer processing, including (i) IP header generation and checking, (ii) detecting data packets with IP addresses directed to the system 100 and otherwise discarding the data packets, (iii) generating IP checksums for outgoing data packets, (iv) checking for valid IP header checksums on incoming data packets, (v) providing (optionally) IP fragmentation and defragmentation capability via the memory 116, (vi) confirming support protocols and packet lengths, and/or (vii) validating the TTL (Time To Live) field has not expired. The circuit 142 may be configured to communicate IP address field information contained in the IP header through the block 144 or the block 146 and circuit 136 to and from the circuit 106. The circuit 106 generally uses the information for the iSCSI/iFC mapping function.
The circuit 144 generally implements the TCP transport layer processing, including TCP header generation and checking. The circuit 144 may be configured to establish a “connection” with an associated state to another device through the IP connection. The circuit 144 generally supports multiple such independent connections. The “state” of a connection, as well as data packets being operated on, will generally be stored in the memory circuit 116 via the interface 114. The TCP processing may include, but is not limited to, (i) generation and checking of the TCP layer checksum, (ii) generation and checking of data packet sequence numbers and acknowledgments per the TCP specifications, and (iii) configurably managing the TCP window size according to various standards or proprietary requirements for increasing or decreasing the window in the face of bandwidth limitations (congestion) and errors. The circuit 144 may be configured to re-sequence received data packets in the correct order prior to delivery to circuit 136. The circuit 144 may be further configured to negotiate a maximum data packet size for the connection and break packets received from circuit 136 into multiple data packets conforming to this maximum packet size. As with circuit 142, the circuit 144 generally communicates TCP port information to and from the circuit 106 as necessary for the iSCSI/iFC mapping function. The above described functions are generally considered normal TCP functions.
The circuit 146 may be configured to implement the UDP header generation and checking functionality. Similarly to circuit 144, the circuit 146 generally provides port address information to and from circuit 106. The circuit 146 is generally configured to generate and/or check the UDP checksum and length in the UDP header for validity.
The interface 110 is implemented as a control interface from the external host circuit 112 to one or more control registers of circuits 140, 142, 144, and 146. The control registers are generally used for error reporting and configurability of the various circuits.
When the system 100 is implemented as the storage controller interface 204, the system 100 may be implemented as a line card, or blade, in the storage controller that connects to either the WAN, or to an Ethernet SAN. The system 100 may be configured to connect an IP interface outside of the storage controller chassis to a bus connecting to the backplane inside the chassis. In the case of the WAN 214, the router 212 will generally be external to the storage controller, and the connection between the two will generally be ethernet at 1 Gbps or 10 Gbps rates. However, other rates may be implemented to meet the design criteria of a particular application. The system 100 may be configured to readily connect directly to the backplane while addressing multiple customers. For example, when the system 100 is connected to a proprietary backplane, the line card may comprise a PCI-x or other interface (e.g., SPI-4, a 10 Gbps interface promoted by the Optical Internetworking Forum).
When the system 100 is implemented as the bridge 210, the system 100 may comprises one or more additional controllers for Fibre Channel, SCSI, and/or possible IDE connectivity. The additional controllers may be implemented either externally or internally to the system 100.
Alternate embodiments of the present invention may include implementing a PCI or PCI-X bus in place of an RIO bus for HAB market and high speed NIC market (non-storage). The IPSec or SSL processing may be embedded. A processor (e.g., an ARM) may be embedded to off-load or eliminate the external host processor 112. The iSCSI/iFC/SCTP functionality may be implemented as part of the system 100. An embedded programmable logic circuit (EPLC) may be incorporated to more easily shift one part between uses (e.g., iSCSI, iFC, video over IP, etc.).
While the invention has been particularly shown and described with reference to the preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6034963||Oct 31, 1996||Mar 7, 2000||Iready Corporation||Multiple network protocol encoder/decoder and data processor|
|US20040111523 *||Nov 2, 2001||Jun 10, 2004||Howard Hall||Tcp/udp acceleration|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7330924||Jan 21, 2005||Feb 12, 2008||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—physical layer interface|
|US7366807||Jan 21, 2005||Apr 29, 2008||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—statistics interface|
|US7376774||Jan 21, 2005||May 20, 2008||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—host interface control generator|
|US7421528||Oct 31, 2006||Sep 2, 2008||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—address filter|
|US7461193||Jan 21, 2005||Dec 2, 2008||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—receive-side client interface|
|US7467319||Jan 21, 2005||Dec 16, 2008||Xilinx, Inc.||Ethernet media access controller embedded in a programmable logic device—clock interface|
|US7474666||Sep 3, 2003||Jan 6, 2009||Cisco Technology, Inc.||Switch port analyzers|
|US7484022||Jan 21, 2005||Jan 27, 2009||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—host interface|
|US7493511||Jan 21, 2005||Feb 17, 2009||Xilinx, Inc.||Network media access controller embedded in a programmable logic device—transmit-side client interface|
|US7535913 *||Jun 5, 2003||May 19, 2009||Nvidia Corporation||Gigabit ethernet adapter supporting the iSCSI and IPSEC protocols|
|US7587587 *||Dec 4, 2003||Sep 8, 2009||Broadcom Corporation||Data path security processing|
|US7590135 *||Dec 30, 2002||Sep 15, 2009||Intel Corporation||Methods and apparatus to perform security related operations on received signals|
|US7620047||Nov 23, 2004||Nov 17, 2009||Emerson Network Power - Embedded Computing, Inc.||Method of transporting a RapidIO packet over an IP packet network|
|US7631107 *||May 12, 2004||Dec 8, 2009||Pandya Ashish A||Runtime adaptable protocol processor|
|US7649885||May 6, 2002||Jan 19, 2010||Foundry Networks, Inc.||Network routing system for enhanced efficiency and monitoring capability|
|US7657703||Apr 28, 2005||Feb 2, 2010||Foundry Networks, Inc.||Double density content addressable memory (CAM) lookup scheme|
|US7738450||Jul 25, 2007||Jun 15, 2010||Foundry Networks, Inc.||System architecture for very fast ethernet blade|
|US7742500 *||Mar 22, 2002||Jun 22, 2010||Gemalto Sa||Method for transmitting data by a mobile station comprising a step of determining a Maximum Datagram Size (MDS)|
|US7761643||Jan 12, 2009||Jul 20, 2010||Xilinx, Inc.||Network media access controller embedded in an integrated circuit host interface|
|US7782784 *||Apr 7, 2003||Aug 24, 2010||Cisco Technology, Inc.||Port analyzer adapter|
|US7813365||Nov 14, 2005||Oct 12, 2010||Foundry Networks, Inc.||System and method for router queue and congestion management|
|US7813367||Jan 8, 2007||Oct 12, 2010||Foundry Networks, Inc.||Pipeline method and system for switching packets|
|US7817659||Mar 26, 2004||Oct 19, 2010||Foundry Networks, Llc||Method and apparatus for aggregating input data streams|
|US7830884||Sep 12, 2007||Nov 9, 2010||Foundry Networks, Llc||Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability|
|US7848253||Mar 19, 2008||Dec 7, 2010||Mcdata Corporation||Method for scoring queued frames for selective transmission through a switch|
|US7899048||Jan 15, 2003||Mar 1, 2011||Cisco Technology, Inc.||Method and apparatus for remotely monitoring network traffic through a generic network|
|US7903654||Dec 22, 2006||Mar 8, 2011||Foundry Networks, Llc||System and method for ECMP load sharing|
|US7917682 *||Jun 27, 2007||Mar 29, 2011||Emulex Design & Manufacturing Corporation||Multi-protocol controller that supports PCIe, SAS and enhanced Ethernet|
|US7934038||Jul 25, 2008||Apr 26, 2011||Xilinx, Inc.||Embedded network media access controller|
|US7948872||Mar 9, 2009||May 24, 2011||Foundry Networks, Llc||Backplane interface adapter with error control and redundant fabric|
|US7953922||Dec 16, 2009||May 31, 2011||Foundry Networks, Llc||Double density content addressable memory (CAM) lookup scheme|
|US7953923||Dec 16, 2009||May 31, 2011||Foundry Networks, Llc||Double density content addressable memory (CAM) lookup scheme|
|US7974208||May 10, 2010||Jul 5, 2011||Foundry Networks, Inc.||System and method for router queue and congestion management|
|US7978614||Dec 10, 2007||Jul 12, 2011||Foundry Network, LLC||Techniques for detecting non-receipt of fault detection protocol packets|
|US7978702||Feb 17, 2009||Jul 12, 2011||Foundry Networks, Llc||Backplane interface adapter|
|US7991937||Oct 31, 2008||Aug 2, 2011||Xilinx, Inc.||Network media access controller embedded in a programmable device—receive-side client interface|
|US7995580||Mar 9, 2009||Aug 9, 2011||Foundry Networks, Inc.||Backplane interface adapter with error control and redundant fabric|
|US8014315||Oct 21, 2009||Sep 6, 2011||Mcdata Corporation||Method for scoring queued frames for selective transmission through a switch|
|US8037399||Jul 18, 2007||Oct 11, 2011||Foundry Networks, Llc||Techniques for segmented CRC design in high speed networks|
|US8055895 *||Aug 31, 2009||Nov 8, 2011||Broadcom Corporation||Data path security processing|
|US8090901||May 14, 2009||Jan 3, 2012||Brocade Communications Systems, Inc.||TCAM management approach that minimize movements|
|US8149839||Aug 26, 2008||Apr 3, 2012||Foundry Networks, Llc||Selection of trunk ports and paths using rotation|
|US8155011||Dec 10, 2007||Apr 10, 2012||Foundry Networks, Llc||Techniques for using dual memory structures for processing failure detection protocol packets|
|US8165136||Apr 25, 2005||Apr 24, 2012||Cisco Technology, Inc.||Virtual port based SPAN|
|US8170025||Nov 26, 2008||May 1, 2012||Cisco Technology, Inc.||Switch port analyzers|
|US8170044||Jun 7, 2010||May 1, 2012||Foundry Networks, Llc||Pipeline method and system for switching packets|
|US8194666||Jan 29, 2007||Jun 5, 2012||Foundry Networks, Llc||Flexible method for processing data packets in a network routing system for enhanced efficiency and monitoring capability|
|US8238255||Jul 31, 2007||Aug 7, 2012||Foundry Networks, Llc||Recovering from failures without impact on data traffic in a shared bus architecture|
|US8271859||Jul 18, 2007||Sep 18, 2012||Foundry Networks Llc||Segmented CRC design in high speed networks|
|US8395996||Dec 10, 2007||Mar 12, 2013||Foundry Networks, Llc||Techniques for processing incoming failure detection protocol packets|
|US8448162||Dec 27, 2006||May 21, 2013||Foundry Networks, Llc||Hitless software upgrades|
|US8493988||Sep 13, 2010||Jul 23, 2013||Foundry Networks, Llc||Method and apparatus for aggregating input data streams|
|US8509236||Aug 26, 2008||Aug 13, 2013||Foundry Networks, Llc||Techniques for selecting paths and/or trunk ports for forwarding traffic flows|
|US8514716||Jun 4, 2012||Aug 20, 2013||Foundry Networks, Llc||Backplane interface adapter with error control and redundant fabric|
|US8599850||Jan 7, 2010||Dec 3, 2013||Brocade Communications Systems, Inc.||Provisioning single or multistage networks using ethernet service instances (ESIs)|
|US8619781||Apr 8, 2011||Dec 31, 2013||Foundry Networks, Llc||Backplane interface adapter with error control and redundant fabric|
|US8671219||May 7, 2007||Mar 11, 2014||Foundry Networks, Llc||Method and apparatus for efficiently processing data packets in a computer network|
|US8718051||Oct 29, 2009||May 6, 2014||Foundry Networks, Llc||System and method for high speed packet transmission|
|US8730961||Apr 26, 2004||May 20, 2014||Foundry Networks, Llc||System and method for optimizing router lookup|
|US8811214||Apr 9, 2012||Aug 19, 2014||Cisco Technology, Inc.||Virtual port based span|
|US8811390||Oct 29, 2009||Aug 19, 2014||Foundry Networks, Llc||System and method for high speed packet transmission|
|US8850223 *||Dec 20, 2002||Sep 30, 2014||F5 Networks, Inc.||Method and system for hard disk emulation and cryptographic acceleration on a blade server|
|US8964754||Nov 8, 2013||Feb 24, 2015||Foundry Networks, Llc||Backplane interface adapter with error control and redundant fabric|
|US8989202||Feb 16, 2012||Mar 24, 2015||Foundry Networks, Llc||Pipeline method and system for switching packets|
|US9015467||Dec 4, 2003||Apr 21, 2015||Broadcom Corporation||Tagging mechanism for data path security processing|
|US9030937||Jul 11, 2013||May 12, 2015||Foundry Networks, Llc||Backplane interface adapter with error control and redundant fabric|
|US9030943||Jul 12, 2012||May 12, 2015||Foundry Networks, Llc||Recovering from failures without impact on data traffic in a shared bus architecture|
|US9112780||Feb 13, 2013||Aug 18, 2015||Foundry Networks, Llc||Techniques for processing incoming failure detection protocol packets|
|US9129043||May 15, 2012||Sep 8, 2015||Ashish A. Pandya||100GBPS security and search architecture using programmable intelligent search memory|
|US9141557||Jun 12, 2014||Sep 22, 2015||Ashish A. Pandya||Dynamic random access memory (DRAM) that comprises a programmable intelligent search memory (PRISM) and a cryptography processing engine|
|US9166818||Nov 18, 2013||Oct 20, 2015||Brocade Communications Systems, Inc.||Provisioning single or multistage networks using ethernet service instances (ESIs)|
|US9338100||Jun 24, 2013||May 10, 2016||Foundry Networks, Llc||Method and apparatus for aggregating input data streams|
|US9378005||Apr 12, 2013||Jun 28, 2016||Foundry Networks, Llc||Hitless software upgrades|
|US9461940||Jul 9, 2014||Oct 4, 2016||Foundry Networks, Llc||System and method for high speed packet transmission|
|US9589158||Aug 18, 2015||Mar 7, 2017||Ashish A. Pandya||Programmable intelligent search memory (PRISM) and cryptography engine enabled secure DRAM|
|US20040131083 *||Mar 22, 2002||Jul 8, 2004||Francois-Xavier Arques||Method for data transmission by a mobile station comprising a datagram size (mds) determination|
|US20040139313 *||Dec 4, 2003||Jul 15, 2004||Buer Mark L.||Tagging mechanism for data path security processing|
|US20040143734 *||Dec 4, 2003||Jul 22, 2004||Buer Mark L.||Data path security processing|
|US20040153854 *||Apr 7, 2003||Aug 5, 2004||Andiamo Systems, Inc.||Port analyzer adapter|
|US20040187107 *||Dec 30, 2002||Sep 23, 2004||Beverly Harlan T.||Techniques to interconnect chips|
|US20040210320 *||May 12, 2004||Oct 21, 2004||Pandya Ashish A.||Runtime adaptable protocol processor|
|US20050053073 *||Sep 3, 2003||Mar 10, 2005||Andiamo Systems, Inc. A Delaware Corporation||Switch port analyzers|
|US20060109845 *||Nov 23, 2004||May 25, 2006||Sandy Douglas L||Method of transporting a RapidIO packet over an IP packet network|
|US20060114933 *||Dec 1, 2004||Jun 1, 2006||Sandy Douglas L||Method of transporting an IP packet over a RapidIO network|
|US20070253420 *||May 21, 2007||Nov 1, 2007||Andrew Chang||Backplane interface adapter|
|US20090003361 *||Jun 27, 2007||Jan 1, 2009||Emulex Design & Manufacturing Corporation||Multi-protocol controller that supports PCle, SAS and enhanced ethernet|
|US20090319775 *||Aug 31, 2009||Dec 24, 2009||Broadcom Corporation||Data Path Security Processing|
|US20100135312 *||Oct 21, 2009||Jun 3, 2010||Mitchem W Jeffrey||Method for Scoring Queued Frames for Selective Transmission Through a Switch|
|US20110179235 *||Jan 20, 2011||Jul 21, 2011||Prolific Technology Inc.||Driving device and method of accessing data by using the same|
|U.S. Classification||370/469, 710/313, 370/389|
|International Classification||H04L12/28, H04L29/06, H04J3/16|
|Cooperative Classification||H04L69/161, H04L69/16, H04L69/169, H04L69/166|
|European Classification||H04L29/06J13, H04L29/06J3, H04L29/06J19, H04L29/06J|
|Jun 25, 2001||AS||Assignment|
Owner name: LSI LOGIC CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VOGEL, DANNY C..;SEEMAN, CLINTON P.;REEL/FRAME:011955/0580
Effective date: 20010622
|Apr 17, 2009||FPAY||Fee payment|
Year of fee payment: 4
|Jul 27, 2011||AS||Assignment|
Owner name: NETAPP, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LSI LOGIC CORPORATION;REEL/FRAME:026661/0205
Effective date: 20110506
|Apr 25, 2013||FPAY||Fee payment|
Year of fee payment: 8
|Sep 14, 2015||AS||Assignment|
Owner name: NETAPP, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LSI LOGIC CORPORATION;REEL/FRAME:036552/0557
Effective date: 20110506
|Apr 25, 2017||FPAY||Fee payment|
Year of fee payment: 12