Abstract:
A method for processing a Get Identifier (“GI_A”) command received by a switch module of a multi-module fiber channel switch with a plurality of switch modules is provided. The method comprises determining if a domain value in the GI_A command is that of the multi-module switch; and if the domain value is equal to that of the multi-module fiber channel switch and if the GI_A command is not sent by one of the plurality of switch modules of the multi-module fiber channel switch, then combining replies from the plurality of switch modules of the multi-module switch with a reply of the switch module receiving the GI_A command; and sending the combined reply to a source of the GI_A command.

Description:
BACKGROUND 
     1. Field of the Invention 
     The present invention relates to fibre channel switches, and more particularly to using distributed Name Server data in multi-module fibre channel switches. 
     2. Background of the Invention 
     Fibre channel is a set of American National Standard Institute (ANSI) standards which provide a serial transmission protocol for storage and network protocols such as HIPPI, SCSI, IP, ATM and others. Fibre channel provides an input/output interface to meet the requirements of both channel and network users. 
     Fibre channel supports three different topologies: point-to-point, arbitrated loop and fibre channel fabric. The point-to-point topology attaches two devices directly. The arbitrated loop topology attaches devices in a loop. The fibre channel fabric topology attaches host systems directly to a fabric, which are then connected to multiple devices. The fibre channel fabric topology allows several media types to be interconnected. 
     Fibre channel fabric devices include a node port or “N_Port” that manages fabric connections. The N_port establishes a connection to a fabric element (e.g., a switch) having a fabric port or F_port. Fabric elements handle routing, error detection, recovery, and similar management functions. 
     Fibre channel is a closed system that relies on multiple ports to exchange information on attributes and characteristics to determine if the ports can operate together. If the ports can work together, they define the criteria under which they communicate. 
     In fibre channel, a path is established between two nodes where the path&#39;s primary task is to transport data from one point to another at high speed with low latency, performing only simple error detection in hardware. The fibre channel switch provides circuit/packet switched topology by establishing multiple simultaneous point-to-point connections. 
     A fibre channel switch is a multi-port device where each port manages a simple point-to-point connection between itself and its attached system. Each port can be attached to a server, peripheral, I/O subsystem, bridge, hub, router, or even another switch. A switch receives a message from one port and automatically routes it to another port. Multiple calls or data transfers happen concurrently through the multi-port fibre channel switch. 
     Fibre channel switches may use multiple modules (also referred to as “blades”) connected by fibre channel ports. Conventionally, a multi-module switch is integrated as a single switch and appears to other devices in the fibre channel fabric as a single switch. 
     Fibre Channel Generic Services (FC-GS-3) specification describes in section 5.0 various fibre channel services that are provided by fibre channel switches including using the “Name Server” to discover fibre channel devices coupled to a fabric. 
     A Name server provides a way for N_Ports and NL_Ports to register and discover fibre channel attributes. Request for Name server commands are carried over the Common Transport protocol, also defined by FC-GS-3. The Name server information is distributed among fabric elements and is made available to N_Ports and NL_Ports after the ports have logged in. 
     Various commands are used by the Name Server protocol, as defined by FC-GS-3, for registration, de-registration and queries. 
     Fiber Channel Switched Fabric (FC-SW-2) specification describes how a Fabric consisting of multiple switches implements a distributed Name Server. 
     The current fibre channel standards or conventional techniques do not provide an efficient way to share Name Server data among the blades, such that the multi-module switch appears to the rest of the fabric as a single switch. 
     In addition, the Fiber Channel standards do not provide any method for sharing Name Server information on multiple independent switch modules that are part of the same switch. 
     Therefore, what is required is a process and system that allows multiple switch modules to implement Name Server commands so that the multiple switch modules appear as one switch to the rest of the Fabric. 
     SUMMARY OF THE INVENTION 
     In one aspect, the present invention allows a group of switch modules to be combined into a single switch for Name Server operations and hence allows efficient execution of Name Server commands. 
     In one aspect of the present invention, a method for processing a Get All Next (“GA_NXT”) Server command in a multi-module fibre channel switch is provided. The method includes, determining if the command is from an N-Port; sending the command to other switches and switch modules within the multi-module switch; determining if replies received from other switch modules and/or switches are better than a current reply; and sending the current reply if the received reply is not better than the current reply. 
     The method further includes, sending the current reply to a command source if the command is not from an N-Port or from another switch module. 
     The method also includes, sending the received reply to the command source if the received reply is better than the current reply. 
     In another aspect of the present invention, a method for processing a Get Identifier (“GI_A”) command in a multi-module fibre channel switch is provided. The method includes, determining if a domain value in the command is that of a local switch module receiving the command; and preparing a reply to the command based on replies from other switch modules if the command is not received from an external switch. 
     The method also includes, sending the command to switch modules with a domain value greater than zero and the domain value in the command matches the switch module; and sending a reply to the switch module with the matching domain value. 
     The method also includes, sending a list of domains, if the domain value of the command is equal to zero. 
     In yet another aspect of the present invention, a method for processing Gxx_ID commands in a multi-module switch operationally coupled in a fibre channel system is provided. The method includes, determining if the command is received from an N-Port, if a port identification value in the command is not the same as that of a multi-module switch that receives the command; and sending the command to a switch whose port identification matches with the port identification value in the command. 
     The method further includes, determining if the command is received from an external fibre channel switch; and sending the command to a switch whose port identification value matches with the port identification value of the command. 
     In yet another aspect of the present invention, a method for processing a command that searches for a Name Server object (GID_PN etc.) by a multi-module fibre channel switch in a fibre channel system is provided. The method includes, determining if the port identifier command is received from an N-Port; sending the command to other switches and switch modules, if the command is from an N-Port; and sending successful replies, if any, received from the switches and/or switch modules. 
     The method also includes, determining if the port identifier command is received from an external switch, if the port identifier command is not from an N_Port;
         sending the command to other switch modules, if the command was received from an external switch; or   sending an error message if the command was not received from an external switch.       

     In yet another aspect of the present invention, a method for processing a port identifier command that returns a list of port identifiers (GID_FT etc., described below) by a multi-module fibre channel switch in a fibre channel system is provided. The method includes, determining if the port identifier command is received from an N-Port; sending the port identifier command to other switches and switch modules, if the port identifier command is from an N-Port; and sending data combined from the replies, if any, received from the switches and/or switch modules. 
     The method also includes, determining if the port identifier command is received from an external switch,
         sending the command to other switch modules, if the command was received from an external switch; or   sending just local switch module reply data if the port identifier command was not received from an external switch.       

     This brief summary has been provided so that the nature of the invention may be understood quickly. A more complete understanding of the invention can be obtained by reference to the following detailed description of the preferred embodiments thereof concerning the attached drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The foregoing features and other features of the present invention will now be described with reference to the drawings of a preferred embodiment. In the drawings, the same components have the same reference numerals. The illustrated embodiment is intended to illustrate, but not to limit the invention. The drawings include the following Figures: 
         FIG. 1 , as described above, shows a block diagram of a fibre channel system using a fibre channel fabric; 
         FIG. 2  is a block diagram showing multi-module switch; 
         FIG. 3  is block diagram of a switch module in a multi-module switch environment, according to one aspect of the present invention; 
         FIGS. 4A and 4B  shows a flow diagram of the overall process for handling Name Server commands in a multi-module fibre channel switch, according to one aspect of the present invention; 
         FIG. 5  is a flow diagram of processing GA-NXT commands in a multi-module fibre channel switch, according to one aspect of the present invention; 
         FIG. 6  is a flow diagram of processing GI_A commands in a multi-module fibre channel switch, according to one aspect of the present invention; 
         FIG. 7  is a flow diagram of processing Gxx_ID commands (Name Server commands that request data associated with a particular Fiber Channel N-Port ID) in a multi-module fibre channel switch, according to one aspect of the present invention; 
         FIG. 8  is a flow diagram is a flow diagram of processing GID_FT and other commands in a multi-module fibre channel switch, according to one aspect of the present invention; and 
         FIG. 9  is a flow diagram is a flow diagram of processing GID_PN and other commands in a multi-module fibre channel switch, according to one aspect of the present invention. 
     
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     Definitions 
     The following definitions are provided as they are typically (but not exclusively) used in the fibre channel environment, implementing the various adaptive aspects of the present invention.
         “Blade”: A module in a fibre channel switch.   “Blade_Id”: A unique identifier for identifying a switch module.   “EBP”: Exchange Blade Parameters, created by Multi-Blade Protocol   “Fibre channel ANSI Standard”: The standard describes the physical interface, transmission and signaling protocol of a high performance serial link for support of other high level protocols associated with IPI, SCSI, IP, ATM and others.   “FC-1”: Fibre channel transmission protocol, which includes serial encoding, decoding and error control.   “FC-2”: Fibre channel signaling protocol that includes frame structure and byte sequences.   “FC-3”: Defines a set of fibre channel services that are common across plural ports of a node.   “FC-4”: Provides mapping between lower levels of fibre channel, IPI and SCSI command sets, HIPPI data framing, IP and other upper level protocols.   “Fabric”: A system which interconnects various ports attached to it and is capable of routing fibre channel frames by using destination identifiers provided in FC-2 frame headers.   “Fabric Topology”: This is a topology where a device is directly attached to a fibre channel fabric that uses destination identifiers embedded in frame headers to route frames through a fibre channel fabric to a desired destination.   Multi Blade protocol: A protocol that operates on internal switch module ports to assign a primary blade.   Port: A general reference to N. Sub.-- Port or F.Sub.--Port.       

     The Fibre Channel Specification used to build one embodiment of the present invention includes:
         FC-SW-2; and   FC-GS-3, standards as published by the American National Standard Institute.       

     To facilitate an understanding of the preferred embodiment, the general architecture and operation of a fibre channel system will be described. The specific architecture and operation of the preferred embodiment will then be described with reference to the general architecture of the fibre channel system. 
       FIG. 1  is a block diagram of a fibre channel system  100  implementing the methods and systems in accordance with the adaptive aspects of the present invention. System  100  includes plural devices that are interconnected. Each device includes one or more ports, classified as node ports (N_Ports), fabric ports (F_Ports), and expansion ports (E_Ports). Node ports may be located in a node device, e.g. server  103 , disk array  105  and storage device  104 . Fabric ports are located in fabric devices such as switch  101  and  102 . Arbitrated loop  106  may be operationally coupled to switch  101  using arbitrated loop ports (FL Ports). 
     The devices of  FIG. 1  are operationally coupled via “links” or “paths”. A path may be established between two N_ports, e.g. between server  103  and storage  104 . A packet-switched path may be established using multiple links, e.g. an N-Port in server  103  may establish a path with disk array  105  through switch  102 . 
     Switch  101  includes an E_Port that enables a path to another switch  102 . An inter-switch link (“ISL”) enables N_Ports to operationally couple to other N-Ports in a fabric. 
       FIG. 2  is a block diagram that shows plural switch modules (or blades)  102 A- 102 F integrated into a single multi-module switch  200 . Internal ports between the switch modules operate on a multi-blade protocol, while external ports operate under FC-SW-2 protocol. 
       FIG. 3  is a block diagram of a blade in a multi-module switch, e.g. blade  102 A, that implements the adaptive aspects of the present invention. Switch module  102 A includes plural external ports (F_Ports operationally coupled to other devices, e.g. server  103 ; or E_Ports coupled to other switch modules)  300 A through  300 D; and internal ports  301 A- 301 D that operate under the multi-blade protocol. 
     Switch module  102 A also includes processor  302  to execute the process steps described below. Processor  302  may be a Pentium™ Class sold by Intel Corporation, or any other processor may be used to implement the adaptive aspects of the present invention. Processor  302  can access memory  303  via bus  302 A. In one aspect of the present invention, memory  303  can store Name Server data  304 A, as well as the executable process steps of the present invention. 
     For a multi-module switch  200 , each switch module ( 102 A- 102 F) maintains Name Server data  304 A for devices attached to its internal ports. Fibre channel frames addressed to a switch module are identified by a special address of hex values ‘FFF8xx’ where “xx” is the module&#39;s slot number. 
     Each switch module ( 102 A- 102 F) stores Name Server  304  for external N-ports that are logged in to that switch module. Distributed Name Server  304  includes Name Server data  304 A and the Name Server code (not shown) executed by processor  302  and adds an extra layer of distribution to get Name Server data  304 A from other switch modules on the same switch. Distributed Name Server  304  commands that are sent to other switch modules on the same switch may use a Blade Controller address (0xFFF8xx, where ‘xx’ is the slot number of the switch module). 
     A switch module that sends distributed Name Server  304  commands to other switches or switch modules assigns a value in the IN_ID field of the CT Header (as defined in FC-GS-3) to match replies to the original command. All other switches or switch modules that get distributed Name Server  304  commands preserve the IN_ID field in the replies. 
     A distributed Name Server  304  control block structure (is a part of Name Server data) (dns_cb) is defined for keeping track of distributed Name Server processing. 
     Distributed Name Server Processing: 
     Distributed Name Server  304  commands may be received from N-Ports, other switches, or other switch modules on the same switch. Process flow for each of them is described below, according to one aspect of the present invention. 
     The following provides a list of Name Server  304  commands that are processed per FC-GS-3, FC-SW-2 and the executable process steps described below with respect to  FIGS. 4A-9   
     Get All Next (“GA_NXT”) (Section 5.1.4.1 of FC-GS-3): 
     A request to obtain Name Server  304  objects associated with a specific Port identifier uses this query. Typically, Name Server  304  returns all Name Server  304  object(s) for the next higher valued Port Identifier registered with Name Server  304 . The format of a GA-NXT request is provided in the aforementioned section of FC-GS-3. 
     Get Identifiers (“GI_A”) (Section 5.14.2 of FC-GS-3): Name Server  304  returns identifiers after this request is received. This command allows a user of Name Server  304  to determine which domains and areas are available for use in the Domain_ID Scope field. The format of the query is provided in the aforementioned section of FC-GS-3. 
     GPN_ID (Get Port name ID), GNN_ID (Get Node Name ID), GCS_ID (Get Class of Service ID), GFT_ID (Get FC-4 Types), GPT_ID, (Get Port Type) GSPN_ID (Get Symbolic Port Name), GIPP_ID (Get IP Address), GFPN_ID (Get Fabric Port Name), GHA_ID (Get Hard Address), GFD_ID (Get FC-4 Descriptors), GFF_ID (Get FC-4 Features) Commands. 
     These commands are described in Sections 5.1.4.3 through 5.1.4.13 of FC-GS-3 and specify a fibre channel address. The processing of these commands is described below with respect to  FIG. 7 . 
     GID_PN (Get Port Identifier), GIPP_PN (Get IP address (Port)), GID_NN (Get Port Identifiers), GPN_NN (Get Port Names), GIP_NN (Get IP address (Node)), GIPA_NN (Get Initial Process Associator), GSNN_NN (Get Symbolic Node Name), GNN_IP (Get Node Name), GIPA_IP, (Get Initial Process Associator), GID_FT (Get Port Identifiers), GPN_FT (Get Port Names), GNN_FT (Get Node Names), GID_PT (Get Port Identifiers), GID_IPP (Get Port Identifier), GPN_IPP (Get Port Name), GID_FF (Get Port Identifiers). 
     The foregoing commands are described (including the command format(s)) in sections 5.1.4.14 through 5.1.4.29 of FC-GS-3 respectively. The commands are Name Server  304  queries seeking specific information, as discussed in the foregoing relevant sections. The execution of the commands in a multi-module switch, according to one aspect of the present invention is described below. 
     RIP_NN (Register IP address (Node), RIPA_NN (Register Initial Process Associator), RSNN_NN (Register Symbolic Node Name). 
     Section 5.1.4.40 through 5.1.4.42 of FC-GS-3 describe the foregoing commands. The execution of the commands in a multi-module switch, according to one aspect of the present invention is described below. 
       FIGS. 4A-4B  shows an overall flow diagram showing process steps for executing Name Server commands in a multi-module switch, according to one aspect of the present invention. 
     In step S 400 , Name Server commands are received by a switch module (e.g.  102 A) from an N-port or any other source. 
     In step S 401 , if a GA_NXT command is received by switch module  102 A, the process moves to step S 401 A described below with respect to  FIG. 5 . 
     In step S 402 , if a GI_A query is received by switch module  102 A, then the process moves to step S 402 A described below with respect to  FIG. 6 . 
     In step S 403 , if any identifier command (herein after collectively referred to as “Gxx_ID”, which includes, commands GPN_ID (Get Port name ID), GNN_ID (Get Node Name ID), GCS_ID (Get Class of Service ID), GFT_ID (Get FC-4 Types), GPT_ID, (Get Port Type) GSPN_ID (Get Symbolic Port Name), GIPP_ID (Get IP Address), GFPN_ID (Get Fabric Port Name), GHA_ID (Get Hard Address), GFD_ID (Get FC-4 Descriptors), GFF_ID (Get FC-4 Features)) are received by switch module  102 A, then in step S 403 A, the commands are processed, as described below with respect to  FIG. 7 . 
     In step S 404 , if switch module  102 A receives commands GID_PN, GIPP_PN, GIP_NN, GIPA_NN, GSNN_NN, GNN_IP, GIPA_IP, GPN_IPP (collectively referred to as GID_PN etc.) then in step S 404 A, the commands are processed as discussed below with respect to  FIG. 9 . 
     In step S 405 , the process ascertains if there are more commands. 
     In step S 406 , if switch module  102 A receives commands GID_FT, GID_NN, GPN_FT, GPN_NN, GID_PT, GNN_FT, GID_IPP and GID_FF (collectively referred to herein as “GID_FT etc.”), then in step S 406 A, the commands are processed as discussed below with respect to  FIG. 8 . 
     In step S 407 , if switch module  102 A receives RIP_NN, RIPA_NN and RSNN_NN (collectively referred herein as “Rxx_NN”), then in step S 407 A, the commands are processed as discussed below with respect to  FIG. 9 . 
     In step S 408 , if switch module  102 A receives commands RPN_ID, RNN_ID, RCS_ID, RFT_ID, RSPN_ID, RPT_ID, RIPP_ID, RHA_ID, RFD_ID, or RFF_ID (collectively referred to herein as “Rxx_ID”), then in step S 408 A, the commands are processed as discussed below with respect to  FIG. 7 . 
     In step S 409 , switch module  102 A ascertains if a Name Server command was in error and the process ends. 
       FIG. 5  is a flow diagram for processing GA_NXT command (step S 401 A) in a multi-module switch, according to one aspect of the present invention. 
     In step S 500 , a switch module (e.g.  102 A) determines the current, best reply to the received GA_NXT command among N-ports on this module. 
     In step S 501 , switch module  102 A determines if the GA_NXT command was received from a N-Port. If the command was received from a N-Port, then in step S 502 , the command is sent to all other external switches, and in step S 504  to the other switch modules on the local switch (e.g.  200 ). 
     If the command was not received from an N-Port, then in step S 503 , switch module  102 A determines if the command was received from another switch. If the command was received from another switch, then in step S 504 , the command is sent to other switch modules ( 102 B- 102 F) on the local switch. 
     In step S 506 , switch module  102 A determines if a reply to the GA-NXT command has been received from another switch or local switch module(s). If a reply is not received, then switch module  102 A waits for the reply. 
     If a reply is received in step S 506 , then in step S 507 , the reply is compared to the current reply (S 500 ) to determine if the received reply is better than the current reply. If the received reply is better than the current reply, then in step S 509 , the received reply becomes the current reply. 
     In step S 508 , switch module  102 A determines if all replies have been received. If all replies have not been received, then the process goes back to step S 506 . 
     If all replies have been received in step S 508 , then in step S 510 , the current reply is sent to the GA_NXT command source. 
     If the command, GA-NXT was received from another switch module (in step S 503 ), then in step S 505 , a reply is sent to the source of the GA_NXT command. 
       FIG. 6  shows a flow diagram to process GI_A command (step S 402 A), as received by a switch module (e.g.  102 A). 
     In step S 600 , switch module  102 A determines if the domain identification (Domain ID) value is equal to zero. If Domain ID is equal to zero then in step S 601 , a list of domains is sent as a reply to the GI_A command. 
     If the Domain ID value is not equal to zero, then in step S 602 , switch module  102 A determines if the Domain ID value is the same as that of the local switch (e.g.  200 ). If the Domain ID value is not the same, then in step S 604 , the command (GI_A) is sent to the switch with the Domain ID value specified in the command payload. 
     In step S 607 , switch module  102 A receives a response from the switch in step  604  and a reply to GI_A is sent to the source. 
     In step S 602 , if the Domain ID specified in the GI_A command is the same as that of local switch (e.g.  200 ), then in step S 603 , a reply with information from the local switch module is prepared. 
     If the GI_A request is from another switch module ( 102 B- 102 F) as ascertained in step S 605 , then in step S 606 , a reply is sent to the source. 
     If the request is not from another switch module, then the GI_A message is sent to all switch modules ( 102 B- 102 F) in step S 608 . 
     In step S 609 , the replies from the other switch modules are appended to the local reply. When all replies from other switch modules have been received, the combined data is sent as a reply to the original source of the GI_A command in step S 606 . 
       FIG. 7  is a flow diagram of process steps for responding to Gxx-ID commands received by a switch module (e.g.  102 A). 
     In step S 700 , switch module  102 A ascertains if the port ID specified in the source Gxx_ID or Rxx_ID command is same as that of switch module  102 A. If the port ID matches the local switch module  102 A, then in step S 701 , a reply is sent and the process ends in step S 701 A. 
     If the port ID is not that of switch module  102 A, then in step S 702 , switch module  102 A determines if the command is from an N-port. If the command is from an N-port, then in step S 703 , the process determines if a port ID is specified for the local switch (for example, switch  200 ). If a port ID is specified then in step S 704 , the command is sent to the switch module whose port ID is specified. Switch module  102 A waits for a reply in step S 705  and after a reply is received in step S 705 , a response is sent to the source of the command in step S 706 . 
     If a port ID is not on the local switch then in step S 707 , the command is sent to another switch and the process steps S 705  and S 706  are performed. 
     If in step S 702 , the command is not from an N-Port, then in step S 708 , the process ascertains if the command is from an external switch. If the command is from the external switch, then in step S 710 , the process determines if a port ID of a switch module is specified in the command (for example, port ID for switch modules  102 B- 102 F in switch  200 ). Thereafter, process steps S 704 , S 705 , and S 706  are performed. 
     If in step S 708  the command is not from an external switch then in step S 709 , an error response is generated and sent to the command source. 
       FIG. 8  is a flow diagram of process steps in a multi-module switch for responding to GID_FT etc. commands (step S 406 A). These commands generate a list of reply data that matches the search object in the command. 
     In step S 800 , the switch module that gets the command (e.g.  102 A) gets local reply data for the command (for example, a GID_FT command will create a list of any local port IDs whose Name Server data contains the FC-4 type specified in the GID_FT command). 
     In step S 801 , the process determines if the command is from an N-Port. If it is from an N-Port, then the command is sent to all external switches in step S 802 , and to all other switch modules in step S 803 . 
     Thereafter, in step S 804 , switch module  102 A waits for replies from the switches. 
     In step S 805 , response from the external switches and local modules is combined and a reply is sent to the source of the command. 
     If the command is not from an N-Port then in step S 806 , the process determines if the command is from an external switch. If the command is from an external switch, then the process moves to step S 803 , which sends the command to all other switch modules, followed by steps S 804  and S 805 . 
     If the command is not from an external switch, then in step S 807 , the local reply from step S 800  is sent to the command source. 
       FIG. 9  shows a flow diagram for processing GID_PN etc. commands from step S 404 A. 
     Turning in detail to  FIG. 9 , in step S 900 , the process determines if a search key is found on the switch module that receives the command, for example, switch module  102 A. 
     If a search key is found, then in step S 901 , a successful reply is sent to the source command. 
     If a search key is not found in step S 900 , then in step S 902 , the process determines if the command is from an N-Port. If the command is from a N-Port, then in step S 903 , the command is sent to all other switches, and in step S 904 , the command is sent to all the switch modules within the multi-module switches (e.g. switch  200 ). 
     In step S 905  switch module  102 A waits for a reply. 
     In step S 906 , the process determines if any successful replies have been received and in step S 908 , successful replies are sent to the command source. 
     If successful replies are not received, then in step S 907 , failed search results are sent to the command source. 
     If the command is not from an N-Port (step S 902 ), then in step S 909 , the process determines if the command is from an external switch. 
     If the command is from an external switch, then the process moves to step S 904 , and if the command is not from an external switch, then in step S 910 , a failed search result is sent to the command source. 
     In one aspect, the present invention allows a group of switch modules to be combined into a single switch for Name Server operations and hence allows efficient execution of Name Server commands. 
     Although the present invention has been described with reference to specific embodiments, these embodiments are illustrative only and not limiting. Many other applications and embodiments of the present invention will be apparent in light of this disclosure and the following claims.