US7966403B2

Performance profiling for improved data throughput

Summary by NHIP

Dynamic Buffer Reallocation

The system opens a high-performance connection with a first host and a low-performance connection with a second host. It reallocates memory buffers reserved for solicited write data from the first host to store unsolicited write data from the second host during oversubscription.

Claim Score by NHIP

Read claim 16, the broadest

Abstract

A computer-implemented system and method for performance profiling on a target device. The computer-implemented method includes configuring the target device to operate in a first mode or a second mode, and receiving a write command from a host device. When the target device is configured to operate in the first mode, the method includes sending an authorization to send write data to the host device, and receiving write data from the host device. When the target device is configured to operate in the second mode, the method includes allocating a reserved write buffer on the target device, and receiving write data from the host device using the write buffer.

US7966403B2, drawing sheet 1 — Sheet 1 of 13

Term

Term ended

Expired 3 March 2024, 2.6 years ago.

19 claims: 4 independent, 15 dependent

1
A computer-implemented method for oversubscribing write data on a target device, the method comprising:opening, at the target device, a first connection with a first host device in a high-performance mode, wherein opening a first connection includes allocating a number of memory buffers for solicited write data received from the first host device within the target device and additionally reserving a number of other memory buffers for unsolicited write data received from the first host device within the target device;opening a second connection with a second host device in a low-performance mode, wherein opening a second connection includes allocating a number of memory buffers for solicited write data received from the second host device within the target device;and initiating an oversubscription process on the target device for the second connection, wherein initiating an oversubscription process includes reallocating a portion of the memory buffers reserved for the first host device as memory to store unsolicited write data received from the second host device, wherein reallocating includes analyzing use of the memory allocated for solicited write data and using a portion of the memory allocated for solicited write data as memory for unsolicited write data from the second host device, wherein, when the oversubscription process is initiated for one of the connections, the target device receives write data from its corresponding host device in a high-performance mode.
8
A target device for managing network-storage, comprising:a network interface used to couple the device to a network;a memory used to hold write data;a processor, wherein the processor is capable of: opening a first connection with a first host device in a high-performance mode, wherein opening a first connection includes allocating a number of memory buffers for solicited write data received from the first host device within the target device and additionally reserving a number of other memory buffers for unsolicited write data received from the first host device within the target device;opening a second connection with a second host device in a low-performance mode, wherein opening a second connection includes allocating a number of memory buffers for solicited write data received from the second host device within the target device;and initiating an oversubscription process, wherein initiating includes reallocating memory allocated for one of the connections to be used by the other connection, wherein initiating an oversubscription process includes reallocating, for the second connection, a portion of the memory buffers reserved for the first host device as memory to store unsolicited write data received from the second host device, wherein reallocating includes analyzing use of the memory allocated for solicited write data and using a portion of the memory allocated for solicited write data as memory for unsolicited write data received from the second host device;wherein, when the oversubscription process is initiated for one of the connections, the target device receives write data from its corresponding host device in a high-performance mode.
12
A system for transferring data, comprising:a plurality of host devices including a first host device and a second host device;and a target device, wherein the target device includes: a network interface used to couple the device to a network;a memory used to hold write data;a processor, wherein the processor is capable of: opening a first connection with the first host device in a high-performance mode, wherein opening a first connection includes allocating a number of memory buffers for solicited write data received from the first host device within the target device and additionally reserving a number of other memory buffers for unsolicited write data received from the first host device within the target device;opening a second connection with the second host device in a low-performance mode, wherein opening a second connection includes allocating a number of memory buffers for solicited write data received from the second host device within the target device;and initiating an oversubscription process, wherein initiating includes reallocating memory allocated for one of the connections to be used by the other connection, wherein initiating an oversubscription process includes reallocating, for the second connection, a portion of the memory buffers reserved for the first host device as memory to store unsolicited write data received from the second host device, wherein reallocating includes analyzing use of the memory allocated for solicited write data and using a portion of the memory allocated for solicited write data as memory for unsolicited write data from the second host device;wherein each host device sends write data via its respective connection to the target device;and wherein, when the oversubscription process is initiated for one of the connections, the target device receives write data from its corresponding host device in a high-performance mode.
16
Broadest claimClaim Score 28, narrow(NHIP)A non-transitory computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform:opening, at a target device, a first connection with a first host device in a high-performance mode, wherein opening a first connection includes allocating a number of memory buffers for solicited write data received from the first host device within the target device and additionally reserving a number of other memory buffers for unsolicited write data received from the first host device within the target device;opening a second connection with the second host device in a low-performance mode, wherein opening a second connection includes allocating a number of memory buffers for solicited write data received from the second host device within the target device;and initiating an oversubscription process on the target device, wherein initiating includes reallocating memory allocated for one of the connections to be used by the other connection, wherein initiating an oversubscription process includes reallocating, for the second connection, a portion of the memory buffers reserved for the first host device as memory to store unsolicited write data received from the second host device, wherein reallocating includes analyzing use of the memory allocated for solicited write data and using a portion of the memory allocated for solicited write data as memory for unsolicited write data received from the second host device;wherein, when the oversubscription process is initiated for one of the connections, the target device receives write data from its corresponding host device in a high-performance mode.

Independent claims4

45 paragraphs in 5 sections, as filed

FIELD OF THE INVENTION

This application is a divisional of U.S. application Ser. No. 10/371,389, filed on Feb. 21, 2003, now U.S. Pat. No. 7,269,644, issued on Sep. 11, 2007, the entire disclosure of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

In data-processing systems, there is often high data throughput. Such systems typically contain devices that need to transfer, store, or manage large quantities of data. Storage devices, for example, have the capability to store mass quantities of data that is made available to other devices in the system.

In these data-processing systems, large amounts of memory space are needed for the various transfer, storage, and management operations. Because there is such a high volume of data, it may often be difficult to mange this memory space efficiently to achieve optimal system performance. Therefore, the intelligence of such systems will often need to implement various methods of data or flow control.

In a first method, these data-processing systems will perform some form of flow control. For example, in systems that use the Small Computer System Interface (SCSI) protocol and that implement flow control, host devices are not permitted to send unsolicited data. Instead, these host devices must receive authorization (or solicitation) to send data to a target device. Such authorizations that are sent from the target devices are coined “ready-to-transfer,” or “R2T,” commands. Once a host device has received an R2T from the target, it may then (and only then) send data to the target. The systems implementing this method, or other similar methods, of flow control achieve better memory management, because memory space is not allocated for host devices until it is available for use. These systems, however, are not able to achieve as high of a performance for data throughput.

In a second method, these data-processing systems will simply allow certain devices to send commands and data to other devices without much limitation. In this method, there is no real flow control to manage data throughput. While these systems may have good performance, they may encounter memory problems. In order to allow such unconditional and unsolicited data transfer, large amounts of memory space are needed. When this memory space is not managed effectively, there will be insufficient space to hold the high volume of unsolicited data transferred in the system. When memory runs short, error recovery mechanisms will need to be put into effect.

Therefore, for the reasons stated above, and for other reasons stated below which will become apparent to those skilled in the art upon reading and understanding the present specification, there is a need for the present invention.

SUMMARY OF THE INVENTION

Various embodiments of the present invention are provided herein. One embodiment provides a computer-implemented method for performance profiling on a target device. In this embodiment, the computer-implemented method includes configuring the target device to operate in a first mode or a second mode, and receiving a write command from a host device. When the target device is configured to operate in the first mode, the method includes sending an authorization to send write data to the host device, and receiving write data from the host device. When the target device is configured to operate in the second mode, the method includes allocating a reserved write buffer on the target device, and receiving write data from the host device using the write buffer. In one embodiment, configuring the target device to operate in a first mode or a second mode includes configuring the target device to operate in a high-performance mode or a low-performance mode.

This embodiment, as well as other embodiments, will be described in the detailed description below.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1A</figref> shows a block diagram of a system having a number of network entities to implement various embodiments of the present invention.

<figref idref="DRAWINGS">FIG. 1B</figref> shows a flow diagram of the operation of one embodiment of the system shown in <figref idref="DRAWINGS">FIG. 1A</figref>.

<figref idref="DRAWINGS">FIG. 2D</figref> shows a block diagram of a performance profile, according to one embodiment of the performance profile shown in <figref idref="DRAWINGS">FIG. 2C</figref>.

<figref idref="DRAWINGS">FIG. 2E</figref> shows a block diagram of a performance profile, according to one embodiment of the performance profile shown in <figref idref="DRAWINGS">FIG. 2C</figref>.

<figref idref="DRAWINGS">FIG. 3</figref> shows a block diagram of a system having a number of hosts and a high-performance target, according to one embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 4</figref> shows a block diagram of a high-performance target, according to one embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 5</figref> shows a block diagram of an oversubscribed high-performance target, according to one embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 6</figref> shows a use-case diagram of data flow between a host and a low-performance target, according to one embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 7</figref> shows a use-case diagram of data flow between a host and a high-performance target, according to one embodiment of the present invention.

<figref idref="DRAWINGS">FIG. 9</figref> shows a block diagram of a network-based storage system for implementing various embodiments of the present invention.

<figref idref="DRAWINGS">FIG. 10</figref> shows an example screen display for configuring performance profiling, according to one embodiment of the present invention.

DETAILED DESCRIPTION

In the following detailed description of the embodiments, reference is made to the accompanying drawings which form a part hereof, and in which are shown by way of illustration of specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the spirit and scope of the present inventions. It is also to be understood that the various embodiments of the invention, although different, are not necessarily mutually exclusive. For example, a particular feature, structure or characteristic described in one embodiment may be included within other embodiments. The following description is, therefore, not to be taken in a limiting sense.

<figref idref="DRAWINGS">FIG. 1A</figref> shows a block diagram of a system having a number of network entities to implement various embodiments of the present invention. In <figref idref="DRAWINGS">FIG. 1</figref>, system 100 includes network entity 102, network 106, and network entity 108. Network entity 102 is coupled to network 106 via its network interface 104. Network entity 108 is coupled to network 106 via its network interface 110. In one embodiment, network 106 includes a local area network. In one embodiment, network 106 includes a wide area network, such as the Internet. In one embodiment, network entity 102 includes a host computing environment, while network entity 108 includes a target storage environment. In various embodiments, network entities 102 and 106 use various protocols to communicate with network 106. In one embodiment, the Small Computer System Interface (SCSI) protocol is used. In this embodiment, network interfaces 104 and 110 include SCSI network interfaces to interface with network 106. In one embodiment, the Internet SCSI (iSCSI) protocol is used. In this embodiment, network interfaces 104 and 110 include iSCSI network interfaces to interface with network 106.

<figref idref="DRAWINGS">FIG. 1B</figref> shows a flow diagram of the operation of one embodiment of the system shown in <figref idref="DRAWINGS">FIG. 1A</figref>. In this embodiment, network entity 102 includes a host device, and network entity 108 includes a target device. Flow diagram 112 shows a computer-implemented method for performance profiling on the target device. At 114, the target device is configured to operate in a first or second mode. At 116, the target device receives a write command from the host device. At 118, the target device is checked to determine if it is configured in the first or second mode. If configured in the first mode, the target device sends an authorization to send write data to the host device at 120, and then the target device receives write data from the host device at 122. If configured in the second mode, the target device allocates a reserved write buffer at 124, and then receives write data from the host device using the write buffer at 126.

<figref idref="DRAWINGS">FIG. 2A</figref> shows a block diagram of a system having a number of hosts and a target device for implementing various embodiments of the present invention, the target device having one or more rules and one or more configuration profiles. System 200 includes host 202 (“host 1”), host 204 (“host 2”), network 206, and target device 208. Host 202, host 204, and target device 208 are each coupled to network 206. In one embodiment, network 206 includes a local area network. In one embodiment, network 206 includes a wide area network, such as the Internet. In one embodiment, target device 208 includes an additional interface to a storage area network. In one embodiment, target device 208 further includes a routing subsystem. Host 202, host 204, and target device 208 communicate via network 206 using the iSCSI protocol, in one embodiment. Target device 208 contains one or more rules 210, and one or more configuration profiles 212. Configuration profiles 212 contain information regarding the configuration of target device 208. Rules 210 contain operating rules governing the run-time functionality of target device 208.

<figref idref="DRAWINGS">FIG. 2B</figref> shows a block diagram of one or more performance rules and one or more quality of service rules, according to one embodiment of the rules shown in <figref idref="DRAWINGS">FIG. 2A</figref>. <figref idref="DRAWINGS">FIG. 2B</figref> shows only one specific embodiment for rules 210; many other variations may exist in other embodiments. In <figref idref="DRAWINGS">FIG. 2B</figref>, rules 210 includes one or more performance rules 214, and one or more quality of service rules 216. Quality of service rules 216 contain rules that govern the quality of service for data transfer to and from target device 208. Performance rules 214 contain rules that govern the performance for data transfer between target device 208 and other hosts, such as host 202 and host 204.

<figref idref="DRAWINGS">FIG. 2C</figref> shows a block diagram of a performance profile and a quality of service profile, according to one embodiment of the configuration profiles shown in <figref idref="DRAWINGS">FIG. 2A</figref>. <figref idref="DRAWINGS">FIG. 2C</figref> shows only one specific embodiment for configuration profiles 212; many other variations may exist in other embodiments. In <figref idref="DRAWINGS">FIG. 2C</figref>, configuration profiles 212 includes performance profile 218, and quality of service profile 220. Performance profile 218 contains configuration information for the performance characteristics of target device 208. Quality of service profile 220 contains configuration information for the quality of service characteristics of target device 208.

<figref idref="DRAWINGS">FIG. 2D</figref> shows a block diagram of a performance profile, according to one embodiment of the performance profile shown in <figref idref="DRAWINGS">FIG. 2C</figref>. <figref idref="DRAWINGS">FIG. 2D</figref> shows one particular embodiment of performance profile 218. In this embodiment, performance profile 218 includes a performance mode indicator 222. Performance mode indicator 222 can be configured according to one of two modes (in this embodiment): HI or LO. In <figref idref="DRAWINGS">FIG. 2D</figref>, performance mode indicator 222 is configured in the HI mode. Other embodiments may use different variations of entries for performance mode indicator 222. For example, in one embodiment, performance mode indicator 222 may be configured according to a HI, MED, or LO mode.

Target device 208 uses performance profile 218, as shown in <figref idref="DRAWINGS">FIG. 2D</figref>, as follows. Target device 208 includes a network interface that couples the device to network 206. Target device 208 also includes a number of memory buffers that are used to hold write data. Such write data may be obtained from various hosts, such as host 202 or host 204. Performance profile 218 is configured to either a first or second performance mode (such as HI or LO). Rules 210 (and, more particularly, performance rules 214, in one embodiment) are operable on performance profile 218. Performance rules 214 cause target device 208 to reserve a predetermined number of the memory buffers for unsolicited write data sent to target device 208 when performance profile 218 is configured to the first performance mode (such as the HI mode, in one embodiment). The number of memory buffers is, in one embodiment, predetermined from a configuration setting. Alternatively, when performance profile 218 is configured to the second performance mode (such as the LO mode, in one embodiment), performance rules 214 cause target device 208 to use the memory buffers only for solicited write data sent to target device 208. In the second performance mode, hosts must receive authorization, or solicitation from, target device 208 before sending write data to target device 208.

<figref idref="DRAWINGS">FIG. 2E</figref> shows a block diagram of a performance profile, according to one embodiment of the performance profile shown in <figref idref="DRAWINGS">FIG. 2C</figref>. <figref idref="DRAWINGS">FIG. 2E</figref> shows another embodiment for performance profile 218. In this embodiment, performance profile 218 includes a plurality of host entries 224. As shown, “host 1” and “host 2” are included, and each has a corresponding performance mode indicator. “Host 1” has a HI performance mode setting, and “host 2” has a LO performance setting. In this fashion, performance profile 218 is capable of including customized performance settings on a per host basis.

Target device 208 uses performance profile 218, as shown in <figref idref="DRAWINGS">FIG. 2E</figref>, as follows. Target device 208 includes a network interface that couples the device to network 206. Target device 208 also includes a number of memory buffers that are used to hold write data. Such write data may be obtained from various hosts, such as host 202 or host 204. Performance profile 218 has one or more host entries 224 for those hosts configured to send data in a high-performance mode. As shown in <figref idref="DRAWINGS">FIG. 2E</figref>, only “host 1” is configured to send data in a high-performance mode. Rules 210 (and, more particularly, performance rules 214, in one embodiment) are operable on performance profile 218. Performance rules 214 cause target device 208 to reserve a predetermined number of the memory buffers for unsolicited write data sent to target device 208 from those hosts having host entries configured to send data in the high-performance mode. In this embodiment shown in <figref idref="DRAWINGS">FIG. 2E</figref>, target device 208 will reserve a predetermined number of the buffers for unsolicited write data for “host 1,” because “host 1” has an entry configured as “HI.” Performance rules 214 cause target device 208 to use the memory buffers only for solicited write data sent to target device 208 from those hosts not having host entries configured to send data in the high-performance mode (such as “host 2”).

<figref idref="DRAWINGS">FIG. 3</figref> shows a block diagram of a system having a number of hosts and a high-performance target, according to one embodiment of the present invention. <figref idref="DRAWINGS">FIG. 3</figref> shows more of the details of the memory used in certain embodiments of the invention. System 300 includes a number of hosts, such as host 310, host 312, and host 314. Each host is coupled to high-performance target 302. High-performance target 302 is a target device that has been configured to operate in a high-performance mode. High-performance target 302 includes a number of reserved memory regions 304, 306, and 308. In one embodiment, reserved memory regions 304, 306, and 308 include memory buffers. The memory space for these regions is reserved to hold unsolicited write data that is sent from a given host. In the embodiment shown in <figref idref="DRAWINGS">FIG. 3</figref>, a predetermined amount of memory is reserved for each host coupled to target 302. Each host is allocated this amount of reserved memory for sending unsolicited write data to target 302. As shown, memory region 304 is reserved to hold unsolicited write data sent from host 310. Memory region 306 is reserved to hold unsolicited write data sent from host 312. And, memory region 308 is reserved to hold unsolicited write data sent from host 314. In one embodiment, the amount of memory space reserved for each region 304, 306, and 308 is predetermined by configuration. In one embodiment, the amount of memory space is dynamically configurable, and the amount of reserved space may vary from region to region. In one embodiment, the reserved memory regions 304, 306, and 308 are allocated to hosts based on a first-come, first-serve (availability) basis. In this embodiment, if all of the reserved memory regions are already allocated and in use, subsequent hosts will only be able to initiate lower-performance connections with high-performance target 302 (implementing solicited data transfer). Because high-performance target 302 only has a certain amount of reserved memory space for high-performance throughput (in this embodiment), and if all such space is in use (i.e., allocated for existing host connections), subsequent connections can only be configured for the lower-performance mode.

<figref idref="DRAWINGS">FIG. 4</figref> shows a block diagram of a high-performance target, according to one embodiment of the present invention. In this embodiment, high-performance target 400 includes a number of write buffers for holding write data sent to target 400 from various host devices. These write buffers include both normal and reserved buffers. Reserved write buffer 402 is reserved for unsolicited write data, while normal write buffers 404, 406, and 408 are used for solicited write data. Target 400 operates in a high-performance mode, because at least one of its buffers is reserved for unsolicited write data.

<figref idref="DRAWINGS">FIG. 5</figref> shows a block diagram of an oversubscribed high-performance target, according to one embodiment of the present invention. In <figref idref="DRAWINGS">FIG. 5</figref>, high-performance target 400 (from <figref idref="DRAWINGS">FIG. 4</figref>) has been configured as an oversubscribed high-performance target. This oversubscription is configured manually (such as by an administrator), in one embodiment. The oversubscription is automatically configured (such as by the system), in one embodiment. In one embodiment of automatic oversubscription, the system monitors the interaction between target 400 and one or more hosts having connections with target 400 over a period of time, and determines the amount of oversubscription that will be implemented. For example, if one host is only sending read commands to target 400, its allocated buffers could be oversubscribed for high-performance use and allocated to another host connection. Oversubsription uses the memory that has already been reserved for high-performance throughput. Oversubscription, therefore, may increase the number of hosts that can send unsolicited write data to target 400. Oversubscribed target 400 still has reserved write buffer 402 and normal write buffers 404, 406, and 408, but uses reserved write buffer 402 for one or more host connections. Each of these host connections may use reserved write buffer 402 for high-performance throughput. In one embodiment, one or more connections initially configured as low-performance connections may use reserved write buffer 402 for unsolicited data flow when target 400 operates in an oversubscription mode. In one embodiment, oversubscription for target 400 is terminated, or “turned off,” due to certain conditions in the system. Such conditions could include increased write data flow for one or more host connections over a period of time. In such instances, target 400 may no longer be capable of operating in an oversubscribed mode. In this embodiment, reserved write buffer 402 is reverted to reserved use for only a given host connection (e.g., a connection initially configured for high-performance mode).

A general process for implementing oversubscription, such as the oversubscription shown in <figref idref="DRAWINGS">FIG. 4</figref> and <figref idref="DRAWINGS">FIG. 5</figref>, is therefore described as follows, according to one embodiment of the present invention. In this embodiment, a computer-implemented method for oversubscribing write data on a target device includes opening a first connection with a first host device in a high-performance mode, reserving an amount of memory for unsolicited write data received from the first host device, opening a second connection with a second host device in a low-performance mode, and initiating an oversubscription process on the target device for the second connection, wherein such initiating includes using the amount of reserved memory for unsolicited write data received from the second host device. In one embodiment, reserving an amount of memory for unsolicited write data received from the first host device includes reserving a predetermined amount of memory for unsolicited write data received from the first host device. In one embodiment, initiating an oversubscription process on the target device for the second connection includes automatically initiating an oversubscription process on the target device based on an interaction history between the target device and the first host device over a period of time. In one embodiment, the method further comprises terminating the oversubscription process on the target device for the second connection to disallow use of the amount of reserved memory for unsolicited write data received from the second host device.

<figref idref="DRAWINGS">FIG. 6</figref> shows a use-case diagram of data flow between a host and a low-performance target, according to one embodiment of the present invention. <figref idref="DRAWINGS">FIG. 6</figref> illustrates one embodiment of data negotiation between a host and a target. In <figref idref="DRAWINGS">FIG. 6</figref>, use-case diagram 600 begins with the host sending the low-performance target a request for a high-performance connection. Because the target is only configured to operate in a low-performance mode, the target rejects the high-performance connection request, and rather instantiates (or provides acceptance for) a low-performance connection with the host. After the connection is established, the host may then send the low-performance target a write command. Before the host can send any write data, however, it must receive authorization (or solicitation) from the target to send such data. After the target sends such authorization (such as a SCSI “ready-to-transfer” command), the host may send write data. The host must then wait to receive additional authorizations before sending further write data to the target.

<figref idref="DRAWINGS">FIG. 7</figref> shows a use-case diagram of data flow between a host and a high-performance target, according to one embodiment of the present invention. <figref idref="DRAWINGS">FIG. 7</figref> illustrates one embodiment of data negotiation between a host and a target. In <figref idref="DRAWINGS">FIG. 7</figref>, use-case diagram 700 begins with the host sending the high-performance target a request for a high-performance connection. Because the target is configured to operate in a high-performance mode, the high-performance target accepts the high-performance connection request. In one embodiment, the high-performance target only accepts the high-performance connection request if it has available (or unallocated) reserved buffers for high-performance write operations. After the connection is established, the host is able to send a write command to the high-performance target. Because the connection is configured in a high-performance mode, the host is able to send unsolicited write data to the target, without requiring authorization from the target.

A general process for data negotiation, such as shown in the use-case diagrams of <figref idref="DRAWINGS">FIG. 6</figref> and <figref idref="DRAWINGS">FIG. 7</figref>, is therefore described as follows, according to one embodiment of the present invention. In this embodiment, a computer-implemented method for negotiating data transfer between a first network entity and a second network entity begins by initiating a session between the first and second network entities. The first network entity sends a high-performance request for the session to the second network entity. When the second network entity is configured as a high-performance network entity, the second network entity sends an acceptance to the first network entity in response to the high-performance request for the session. The first network entity then sends a write command to the second network entity, and subsequently sends write data. When the second network entity is not configured as a high-performance network entity, the second network entity sends a rejection to the first network entity in response to the high-performance request for the session. In one embodiment, the session is configured as a low-performance session. After the session is established, the first network entity sends a write command to the second network entity. Before the first network entity sends data, the second network entity must first send it an authorization for sending write data. Upon receipt of such authorization, the first network entity is able to send write data to the second network entity.

<figref idref="DRAWINGS">FIG. 8</figref> shows a block diagram of a network entity having an input/output component, memory, a local storage device, and a processor, according to one embodiment of the present invention. In this embodiment, network entity 800 includes processor 802, input/output device 804, memory 806, and local storage device 808. In one embodiment, processor 802, input/output device 804, memory 806, and local storage device 808 are coupled by a network link. In one embodiment, input/output device 804 includes a keyboard and pointing device. In one embodiment, input/output device 804 includes a display. In one embodiment, memory 806 includes both volatile and non-volatile memory. In one embodiment, local storage device 808 includes a mass-storage disk device. Thus, network entity 800 includes various computer-readable media. In one embodiment, network entity 800 includes a host device. In one embodiment, network entity 800 includes a target device.

<figref idref="DRAWINGS">FIG. 9</figref> shows a block diagram of a network-based storage system for implementing various embodiments of the present invention. System 900 includes network entities 902 and 904. In one embodiments, network entities 902 and 904 are host computing devices. Network entities 902 and 904 send data to routing device 908 via network 906. In one embodiment, routing device 908 is a target device. In one embodiment, network 906 is an Internet Protocol (IP) network that is capable of transporting SCSI requests and responses. In one embodiment, iSCSI data is also communicated across network 906. In one embodiment, routing device 908 includes iSCSI interfaces, to route iSCSI requests and responses. In one embodiment, routing device 908 is configured as either a high-performance or a low-performance target device. In one embodiment, one of the network entities 902 or 904 issues a SCSI request and encapsulates the SCSI request in one or more IP packets. The encapsulated SCSI request is routed across IP network 906 to routing device 908, where the SCSI request is extracted from the one or more IP packets. In one embodiment, these IP packets comprise unsolicited write data sent to routing device 908. The extracted SCSI request is then routed through storage network 910 to a storage device (e.g., 912, 914, or 916) In one embodiment, the storage device is a SCSI device. In one embodiment, storage network 910 includes a fibre channel network.

As is shown in <figref idref="DRAWINGS">FIG. 9</figref>, system 900 can be viewed as performing three distinct actions for each request. First, SCSI requests are transported over an IP network. Second, SCSI requests are routed through routing device 908 to storage network 910. Finally, the SCSI request is transported across storage network 910 to a SCSI device (e.g., 912, 914, or 916). In one embodiment, the requests are transmitted in unsolicited fashion, wherein routing device 908 is configured in a high-performance mode. System 900 can also be viewed as performing three distinct actions for each response. First, SCSI responses are transported from a SCSI device (such as 912, 914, or 916) across storage network 910 Second, SCSI responses are routed through routing device 908 to IP network 906. Finally, the SCSI response is transported across IP network 906 to one of the network entities 902 or 904.

<figref idref="DRAWINGS">FIG. 10</figref> shows an example screen display for configuring performance profiling, according to one embodiment of the present invention. In <figref idref="DRAWINGS">FIG. 10</figref>, screen display 1000 shows various configuration parameters for a target device. In one embodiment, the target device is a SCSI target. Particularly, parameter 1002 can be used for configuring performance profiling. Profile parameter 1002 can be set to “Low” or “High.” When set to “Low,” the target operates in a low-performance mode, and memory is utilized for solicited data flow. In one embodiment, a full set of memory buffers are used for solicited data, because none are used (or reserved) for unsolicited data. When set to “High,” the target operates in a high-performance mode. In this mode, a specified amount of memory is reserved for high-performance throughput (in an unsolicited fashion).

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiment shown. This application is intended to cover any adaptations or variations of the described embodiments of the present invention.

Contents5

Every citation, both waysCites: the store holds 14 of 15

Citations
Document	Relation	Office	Cited during
US2002078213A1	Cites	United States of America	Search report
US2002174227A1	Cites	United States of America	Search report
US2003084209A1	Cites	United States of America	Search report
US2003120676A1	Cites	United States of America	Applicant
US2004125806A1	Cites	United States of America	Applicant
US6845403B2	Cites	United States of America	Applicant
US6865617B2	Cites	United States of America	Applicant
US7571209B2	Cites	United States of America	Applicant
US7774449B2	Cites	United States of America	Applicant
US20020078213A1	Cites	United States of America	Search report
US20020174227A1	Cites	United States of America	Search report
US20030084209A1	Cites	United States of America	Search report
US20030120676A1	Cites	United States of America	Third party observation
US20040125806A1	Cites	United States of America	Third party observation
"U.S. Appl. No. 10/371,389, Advisory Action mailed Mar. 12, 2007", 4 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 10/371,389, Final Office Action mailed Nov. 29, 2006", 10 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 10/371,389, Non Final Office Action mailed Jun. 28, 2006", 10 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 10/371,389, Notice of Allowance mailed May 2, 2007", 10 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 10/371,389, Response filed Jan. 26, 2007 to Final Office Action mailed Nov. 29, 2006", 16 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 10/371,389, Response filed Sep. 8, 2006 to Non Final Office Action mailed Jun. 28, 2006", 13 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 11/771,287, Non-Final Office Action mailed Apr. 1, 2008", 7 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 11/771,287, Preliminary Amendment filed Nov. 5, 2007", 7 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 11/771,287, Response filed Jun. 20, 2008 to Non Final Office Action mailed Apr. 1, 2008", 8 pages.	Non-patent	–	Applicant
"U.S. Appl. No. 11/771,287, Supplemental Preliminary Amendment mailed Nov. 5, 2007", 7 pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 11/771,287 Final Office Action Mailed on Nov. 7, 2008", 10 Pgs.	Non-patent	–	Applicant
"U.S. Appl. No. 11/852,849, Preliminary Amendment filed Nov. 5, 2007", 10 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/771,287, Notice of Allowance mailed Apr. 1, 2009, 15 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Non-Final Office Action mailed Mar. 23, 2009, 22 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 10/371,389, Examiner Interview Summary mailed Apr. 12, 2007, 2 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 10/371,389, Examiner Interview Summary mailed Jul. 26, 2007, 1 pg.	Non-patent	–	Applicant
U.S. Appl. No. 11/771,287, Advisory Action mailed Feb. 9, 2009, 4 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/771,287, Preliminary Amendment filed Jul. 2, 2007, 7 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/771,287, Response filed Jan. 23, 2009 to Final Office Action mailed Nov. 7, 2008, 14 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Advisory Action mailed Jan. 22, 2010, 3 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Examiner Interview Summary mailed Mar. 18, 2010, 2 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Final Office Action mailed Oct. 29, 2009, 22 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Notice of Allowance mailed Apr. 5, 2010, 4 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Response filed Jun. 25, 2009 to Non Final Office Action mailed Mar. 23, 2009, 12 pgs.	Non-patent	–	Applicant
U.S. Appl. No. 11/852,849, Response filed Dec. 30, 2009 to Final Office Action mailed Oct. 29, 2009, 14 pgs.	Non-patent	–	Applicant
“U.S. Appl. No. 10/371,389, Advisory Action mailed Mar. 12, 2007”, 4 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 10/371,389, Final Office Action mailed Nov. 29, 2006”, 10 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 10/371,389, Non Final Office Action mailed Jun. 28, 2006”, 10 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 10/371,389, Notice of Allowance mailed May 2, 2007”, 10 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 10/371,389, Response filed Jan. 26, 2007 to Final Office Action mailed Nov. 29, 2006”, 16 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 10/371,389, Response filed Sep. 8, 2006 to Non Final Office Action mailed Jun. 28, 2006”, 13 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/771,287, Non-Final Office Action mailed Apr. 1, 2008”, 7 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/771,287, Preliminary Amendment filed Nov. 5, 2007”, 7 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/771,287, Response filed Jun. 20, 2008 to Non Final Office Action mailed Apr. 1, 2008”, 8 pages.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/771,287, Supplemental Preliminary Amendment mailed Nov. 5, 2007”, 7 pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/771,287 Final Office Action Mailed on Nov. 7, 2008”, 10 Pgs.	Non-patent	–	Third party observation
“U.S. Appl. No. 11/852,849, Preliminary Amendment filed Nov. 5, 2007”, 10 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/771,287, Notice of Allowance mailed Apr. 1, 2009, 15 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Non-Final Office Action mailed Mar. 23, 2009, 22 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 10/371,389, Examiner Interview Summary mailed Apr. 12, 2007, 2 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 10/371,389, Examiner Interview Summary mailed Jul. 26, 2007, 1 pg.	Non-patent	–	Third party observation
U.S. Appl. No. 11/771,287, Advisory Action mailed Feb. 9, 2009, 4 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/771,287, Preliminary Amendment filed Jul. 2, 2007, 7 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/771,287, Response filed Jan. 23, 2009 to Final Office Action mailed Nov. 7, 2008, 14 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Advisory Action mailed Jan. 22, 2010, 3 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Examiner Interview Summary mailed Mar. 18, 2010, 2 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Final Office Action mailed Oct. 29, 2009, 22 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Notice of Allowance mailed Apr. 5, 2010, 4 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Response filed Jun. 25, 2009 to Non Final Office Action mailed Mar. 23, 2009, 12 pgs.	Non-patent	–	Third party observation
U.S. Appl. No. 11/852,849, Response filed Dec. 30, 2009 to Final Office Action mailed Oct. 29, 2009, 14 pgs.	Non-patent	–	Third party observation

7 members in 1 office

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
37138903	United States of America	A	2003-02-21
37138903	United States of America	A	2003-02-21
85286207	United States of America	A	2007-09-10
10371389	–	–	–
US20030371389	–	–	–
US20070852862	–	–	–

Members7

Family members, oldest first
Document	Office	Kind
US7269644B1	United States of America	B1	2007-09-11
US2007299960A1	United States of America	A1	2007-12-27
US2008005289A1	United States of America	A1	2008-01-03
US2008005436A1	United States of America	A1	2008-01-03
US7571209B2	United States of America	B2	2009-08-04
US7774449B2	United States of America	B2	2010-08-10
US7966403B2This record	United States of America	B2	2011-06-21

68 transactions on the USPTO file

Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.

Non-final rejections: 1
Final rejections: 1
RCEs: 1
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2023-07-24	Expire PatentEXP.	EXP.
2023-02-06	Maintenance Fee Reminder MailedREM.	REM.
2018-12-21	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2015-05-15	Email NotificationEML_NTR	EML_NTR
2015-05-15	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2015-05-13	Correspondence Address ChangeC.AD	C.AD
2011-06-21	Recordation of Patent Grant MailedPGM/	PGM/
2011-06-21	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2011-06-02	Email NotificationEML_NTR	EML_NTR
2011-06-01	Issue Notification MailedAllowedWPIR	WPIR
2011-05-13	Dispatch to FDCD1935	D1935
2011-05-13	Dispatch to FDCD1935	D1935
2011-05-12	Application Is Considered Ready for IssuePILS	PILS
2011-05-11	Issue Fee Payment VerifiedN084	N084
2011-05-11	Issue Fee Payment ReceivedIFEE	IFEE
2011-02-11	Electronic ReviewELC_RVW	ELC_RVW
2011-02-11	Email NotificationEML_NTR	EML_NTR
2011-02-11	Email NotificationEML_NTF	EML_NTF
2011-02-11	Mail Examiner's AmendmentMEX.A	MEX.A
2011-02-11	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2011-02-08	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2010-12-19	Examiner's Amendment CommunicationEX.A	EX.A
2010-12-09	Examiner Interview Summary Record (PTOL - 413)EXIN	EXIN
2010-11-03	Email NotificationEML_NTR	EML_NTR
2010-11-03	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2010-10-29	Correspondence Address ChangeC.AD	C.AD
2010-10-27	Date Forwarded to ExaminerFWDX	FWDX
2010-10-27	Disposal for a RCE / CPA / R129AbandonedABN9	ABN9
2010-10-26	Information Disclosure Statement consideredIDSC	IDSC
2010-10-26	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2010-10-26	Reference capture on IDSRCAP	RCAP
2010-10-26	Information Disclosure Statement (IDS) FiledM844	M844
2010-10-26	Request for Continued Examination (RCE)RCEX	RCEX
2010-10-26	Request for Extension of Time - GrantedXT/G	XT/G
2010-10-26	Workflow - Request for RCE - BeginBRCE	BRCE
2010-06-17	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2010-06-08	Mail Notice of Informal or Non-Responsive AmendmentNINA	NINA
2010-06-07	Final RejectionFinal rejectionCTFR	CTFR
2010-03-06	Date Forwarded to ExaminerFWDX	FWDX
2009-07-08	Date Forwarded to ExaminerFWDX	FWDX
2009-06-25	Information Disclosure Statement consideredIDSC	IDSC
2009-06-25	Response after Non-Final ActionA...	A...
2009-06-25	Information Disclosure Statement (IDS) FiledM844	M844
2009-06-25	Informal or Non-Responsive Amendment after Examiner ActionA.I.	A.I.
2009-06-25	Response after Non-Final ActionA...	A...
2009-06-25	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2009-03-25	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2009-03-24	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-12-29	Information Disclosure Statement (IDS) FiledM844	M844
2008-12-29	Reference capture on IDSRCAP	RCAP
2008-12-29	Information Disclosure Statement consideredIDSC	IDSC
2008-12-29	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-10-07	Case Docketed to Examiner in GAUDOCK	DOCK
2008-08-31	Case Docketed to Examiner in GAUDOCK	DOCK
2008-01-03	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2007-11-08	Transfer Inquiry to GAUTI1050	TI1050
2007-11-05	Preliminary AmendmentA.PE	A.PE
2007-11-02	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2007-10-22	Application Dispatched from OIPEOIPE	OIPE
2007-09-25	Sent to Classification ContractorPGPC	PGPC
2007-09-25	Application Is Now CompleteCOMP	COMP
2007-09-14	Cleared by OIPE CSRL194	L194
2007-09-14	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2007-09-10	Information Disclosure Statement consideredIDSC	IDSC
2007-09-10	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-09-10	Reference capture on IDSRCAP	RCAP
2007-09-10	Information Disclosure Statement (IDS) FiledM844	M844
2007-09-10	Initial Exam Team nnIEXX	IEXX

8 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2023-08-15	Lapsed due to failure to pay maintenance feeLapsedFP	FP
2023-07-24	Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS	LAPS
2023-07-24	Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH	STCH
2023-02-06	Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2018-12-21	Maintenance fee paymentMAFP	MAFP
2014-12-22	Fee paymentFPAY	FPAY
2011-06-01	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2010-12-05	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP