Abstract: A system configured to implement Comprehensive Contention-Based Thread Allocation and Placement, may generate a description of a workload from multiple profiling runs and may combine this workload description with a description of the machine's hardware to model the workload's performance over alternative thread placements. For instance, the system may generate a machine description based on executing stress applications and machine performance counters monitoring various performance indicators during execution of a synthetic workload. Such a system may also generate a workload description based on profiling sessions and the performance counters. Additionally, behavior of a workload with a proposed thread placement may be modeled based on the machine description and workload description and a prediction of the workload's resource demands and/or performance may be generated.

Abstract: A system configured to implement Comprehensive Contention-Based Thread Allocation and Placement, may generate a description of a workload from multiple profiling runs and may combine this workload description with a description of the machine's hardware to model the workload's performance over alternative thread placements. For instance, the system may generate a machine description based on executing stress applications and machine performance counters monitoring various performance indicators during execution of a synthetic workload. Such a system may also generate a workload description based on profiling sessions and the performance counters. Additionally, behavior of a workload with a proposed thread placement may be modeled based on the machine description and workload description and a prediction of the workload's resource demands and/or performance may be generated.

Abstract: Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together.

Abstract: Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together.

Abstract: Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together.

Abstract: A system configured to implement detection, modeling and application of memory bandwidth patterns may predict performance of multi-threaded applications with different thread placements. Additionally, such a system may model bandwidth requirements of an application based on placement of the application's threads and may generate a bandwidth signature by sampling performance counters while executing the application using specific thread placement and determining values for multiple classes of bandwidth, such as static, local, per-thread and interleaved. Performance counters may information such as elapsed time, number of instructions executed, and/or the volume of data read or written to each memory bank. A bandwidth signature may be used to apply bandwidth requirements to differing thread placements within various types of systems, such as performance prediction systems, data structure libraries, as well as debugging and development systems.

Abstract: Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together.

Abstract: Adaptive data collections may include various type of data arrays, sets, bags, maps, and other data structures. A simple interface for each adaptive collection may provide access via a unified API to adaptive implementations of the collection. A single adaptive data collection may include multiple, different adaptive implementations. A system configured to implement adaptive data collections may include the ability to adaptively select between various implementations, either manually or automatically, and to map a given workload to differing hardware configurations. Additionally, hardware resource needs of different configurations may be predicted from a small number of workload measurements. Adaptive data collections may provide language interoperability, such as by leveraging runtime compilation to build adaptive data collections and to compile and optimize implementation code and user code together.

Abstract: A system configured to implement detection, modeling and application of memory bandwidth patterns may predict performance of multi-threaded applications with different thread placements. Additionally, such a system may model bandwidth requirements of an application based on placement of the application's threads and may generate a bandwidth signature by sampling performance counters while executing the application using specific thread placement and determining values for multiple classes of bandwidth, such as static, local, per-thread and interleaved. Performance counters may information such as elapsed time, number of instructions executed, and/or the volume of data read or written to each memory bank. A bandwidth signature may be used to apply bandwidth requirements to differing thread placements within various types of systems, such as performance prediction systems, data structure libraries, as well as debugging and development systems.

Abstract: A system configured to implement Comprehensive Contention-Based Thread Allocation and Placement, may generate a description of a workload from multiple profiling runs and may combine this workload description with a description of the machine's hardware to model the workload's performance over alternative thread placements. For instance, the system may generate a machine description based on executing stress applications and machine performance counters monitoring various performance indicators during execution of a synthetic workload. Such a system may also generate a workload description based on profiling sessions and the performance counters. Additionally, behavior of a workload with a proposed thread placement may be modeled based on the machine description and workload description and a prediction of the workload's resource demands and/or performance may be generated.

Abstract: A mobile electronic device such as a mobile phone includes wallet application software for receiving, storing, encrypting, and transmitting selected payment card data. A tab including a programmable magnetic stripe is associated with a controller for receiving transmitted payment card data and programming the stripe with selected data. The tab is mounted directly to the electronic device or to an attachment device removably coupled to the electronic device. The attachment device may comprise a case for the mobile electronic device that allows access to a user interface and display of the mobile electronic device.

Abstract: A mobile electronic device such as a mobile phone includes wallet application software for receiving, storing, encrypting, and transmitting selected payment card data. A tab including a programmable magnetic stripe is associated with a controller for receiving transmitted payment card data and programming the stripe with selected data. The tab is mounted directly to the electronic device or to an attachment device removably coupled to the electronic device. The attachment device may comprise a case for the mobile electronic device that allows access to a user interface and display of the mobile electronic device.

Abstract: A MMIC based superheterodyne receiver for converting at RF energy in an upper and a lower frequency band includes at least one attenuator for the RF energy input, a mixer for mixing the lower band input with a LO1 signal, another mixer for mixing the upper band input with the LO1 signal signal, a switch to direct the LO1 signal to the first mixer or to the second mixer, and a third mixer for mixing a LO2 signal with the first stage mixer output to produce a signal at the output frequency. Passband filters at the outputs of the mixers can reject interfering mixer-generated frequencies. Input frequency range can span 0.1 to 18 GHz with a 160 MHz or 1 GHz output. A modular receiver can have two or more converter modules for each LO module. The receiver can receive antenna input directly, without pre-mixing filtering or attenuating.

Abstract: A wobble drive for imparting reciprocating motion to a sickle bar includes a wobble drive shaft rotatable about a first axis and having a cylindrical wobble section formed about an axis making an angle of about 14.5.degree. to the first axis. A toroidal wobble shaft bearing housing is mounted on the wobble section by a set of wobble bearings having their outer races pressed into the bearing housing. An output yoke is coupled to the wobble shaft bearing housing for transmitting the oscillatory motion of the housing, caused by rotation of the drive shaft, to a swing arm fixed to an end of a shaft portion of the yoke. The coupling of the yoke to the wobble bearing housing is accomplished by a pair of headed spindle pins inserted, from the inside out, through pin bores provided at diametrically opposite locations in the wobble shaft bearing housing, and into respective yoke bearings mounted in the ends of a pair of yoke limbs that are joined to the yoke shaft portion.