Abstract: Systems and methods relate to indexing of performance and cost of workloads in a computing environment. The computing environment may include a virtualized computing environment. According to some embodiments, a performance index relating to a plurality of workloads executing in the computing environment may be generated, where the performance index is based at least in part on performance and cost of use of one or more resources in the computing environment by the plurality of workloads. The index may be normalized. If the performance or cost of a particular workload departs from an expected performance or cost determined from the average performance and/or cost in the computing environment, resources may be reallocated to the workloads such that the performance or cost of the workload is closer to its expected performance or cost based on the performance index.

Abstract: Systems and methods relate to indexing of performance and cost of workloads in a computing environment. The computing environment may include a virtualized computing environment. According to some embodiments, a performance index relating to a plurality of workloads executing in the computing environment may be generated, where the performance index is based at least in part on performance and cost of use of one or more resources in the computing environment by the plurality of workloads. The index may be normalized. If the performance or cost of a particular workload departs from an expected performance or cost determined from the average performance and/or cost in the computing environment, resources may be reallocated to the workloads such that the performance or cost of the workload is closer to its expected performance or cost based on the performance index.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: A first file server for use with a distributed-file system includes a processor configured to determine that an incoming file system communication is associated with a first portion of the distributed-file system associated with a second file server, send a first authorization request to the second file server to request authorization to directly access the first portion of the distributed-file system, analyze a first authorization response from the second file server to determine at least one storage location associated with the first portion of the distributed-file system, determine that an incoming second authorization request received from a third file server is associated with a second portion of the distributed-file system associated with the first file server, obtain data indicative of the second portion of the distributed-file system, and send a second authorization response that includes the data.

Abstract: File system coherency of a file system, particularly for system blocks, may be maintained by (i) duplicating and verifying the (system) blocks, (ii) writing (system) blocks as a sequence of atomic commands so that at any given time, there is a valid (system) block on a physical storage device, and/or (iii) defining the file system directory data structure with directory blocks, each of the directory blocks having at least one of a directory entry and a pointer, where updates to the directory data structure are performed atomically.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: A file system (i) permits storage capacity to be added easily, (ii) can be expanded beyond a given unit, (iii) is easy to administer and manage, (iv) permits data sharing, and (v) is able to perform effectively with very large storage capacity and client loads. State information from a newly added unit is communicated (e.g., automatically and transparently) to central administration and management operations. Configuration and control information from such operations is communicated (e.g., automatically) back down to the newly added units, as well as existing units. In this way, a file system can span both local storage devices (like disk drives) and networked computational devices transparently to clients. Such state and configuration and control information can include globally managed segments as the building blocks of the file system, and a fixed mapping of globally unique file identifiers (e.g., Inode numbers) and/or ranges thereof, to such segments.

Abstract: Disclosed is a pupil aperture, and method for making the pupil aperture for use in a photolithography scanner system. The pupil aperture includes a plate having a set of pole apertures that are radially offset from a reference center point of the plate. The plate further includes a horizontal reference line that intersects the reference center point. The horizontal reference line is used to define a target angle that is between about 15 degrees and about 35 degrees from the horizontal reference line. The target angle defines an off-axis location for each of the set of pole apertures. In a specific aspect of this invention, a set ranging between 3 to 9 pole apertures can be defined in the plate, and their offset from the center point can be selected to be between about 0.3 inches and about 0.9 inches.