262 results about "Thread management" patented technology

Techniques for managing multiple threads in an asynchronous environment, such as a browser, are described. As a method, instantiating an event thread in response to a user event by a shell event handler block that provides shell functions for a user event. Once the event thread as been instantiated, managing the event thread by a generic thread manager block that provides a plurality of multithread management functions for the shell event handler. When required, blocking and unblocking the event thread by a blocking system that is arranged to block and unblock threads.

An apparatus and a method for surgical suturing with thread management. An apparatus for tissue suturing comprising a cartridge having a suturing needle having a pointed end and a blunt end, the suturing needle capable of rotating about an axis; a pusher assembly comprising a cartridge holder having a needle rotation drive capable of releasably engaging the cartridge and rotating the suturing needle about the axis; and an actuator capable of releasably engaging the needle rotation drive to rotate the needle rotation drive. A method for suturing tissue comprising placing a suturing device having a cartridge containing a suturing needle to span separated tissue segments; activating an actuator to cause rotational movement of the suturing needle through the separated tissue segments; and deactivating the actuator to stop an advancing movement of the suturing needle to cause a suturing material to be pulled through the separated tissue segments forming a stitch.

A device, system, and method are directed towards managing threads in a computer system with one or more processing units, each processing unit having a corresponding hardware resource. Threads are characterized based on their use or requirements for access to the hardware resource. The threads are distributed among the processing units in a configuration that leaves at least one processing unit with threads that have an aggregate zero or low usage of the hardware resource. Power may be reduced or turned off to the instances of the hardware resource that have zero or low usage. Distribution may be based on one or more of a number of specifications or factors, such as user power management specifications, power usage, performance, and other factors.

A system for discussion thread management using tag-based categorization, in which three types of tags are provided together to enable effective categorization of discussion threads, based on both automated and manual tagging. The three tag types are 1) user-defined tags, 2) moderator-promoted tags, and 3) system-generated tags. User-defined tags are arbitrarily defined by individual users and associated by users with posts to meet specific user needs. System-generated tags are automatically generated for each sub-thread to summarize a post and all the replies beneath it. System-generated tags can be promoted to a moderator-promoted tags when a moderator user verifies the correctness of a system-generated tag. The disclosed system detects topic changes in discussion threads based on the tags associated with each post in the thread. A moderator can manually examine sub-threads that have been determined to be off topic, and take appropriate actions. For example, a moderator may delete an off topic post or sub-thread, or fork a new thread of discussion for an off-topic sub-thread. Such processing of off-topic sub-threads can alternatively be made by the disclosed system automatically, without moderator intervention. Moderators can also define policies to control discussion moderation based on the disclosed tags and off-topic determinations.

Methods and apparatuses for thread management for multi-threading are described herein. In one embodiment, exemplary process includes selecting, during a compilation of code having one or more threads executable in a data processing system, a current thread having a most bottom order, determining resources allocated to one or more child threads spawned from the current thread, and allocating resources for the current thread in consideration of the resources allocated to the current thread's one or more child threads to avoid resource conflicts between the current thread and its one or more child threads. Other methods and apparatuses are also described.

Described is an application program interface (API) that enables dynamic modification to applications executing in a heterogeneous distributed computing environment. The application program interface includes a navigation function, a query function, a thread management function, and a modifier function. The navigation function returns program information for a local or remote computer (i.e., specified computing device). The query function returns information about a program on the specified computing device. The thread management function controls execution of other programs on the specified computing device. The modifier function modifies a system memory on the specified computing device that stores the heterogeneous program. The API works in conjunction with a hierarchical intermediate representation of the heterogeneous program such that pre-defined program tools can modify the intermediate representation and write these modifications to the specified computing device while the heterogeneous program remains operational.

The present invention provides various simple and easy ways for each end user to manage the thread in a way that suits them. In some cases, the user experience requires only a single click. Additional embodiments allow user to manage inbox space, recover suppressed threads, be alerted on contextual changes of such threads, and so forth. The system allows the user to specifically configure his / her own email thread management scheme by selecting an email and choosing “Suppress Thread” on his / her user interface. The system then performs a number of steps such as examining the <message-id> and <references> headers of the selected email to configure the suppress filter. Once configured, the system will examine each email as it is received and examine its <message-id> and <references> headers per RFC 822. If the headers match the configured <messageid> and <responses> headers, the emails will be suppressed in the manner chosen by the user such as deletion or move to folder.

A multiprocessing system is disclosed. The system includes a multithreading microprocessor including a plurality of thread contexts (TCs), each having a program counter and a general purpose register set for executing a thread. The microprocessor also includes a shared privileged resource, shared by the plurality of TCs rather than being replicated for each of the plurality of TCs, and privileged to be managed only by operating system-privileged threads rather than by user-privileged threads. The system also includes a multiprocessor operating system (OS), configured to manage the shared privileged resource, and to schedule execution of both the operating system-privileged threads and the user-privileged threads on the plurality of TCs.

A mechanism to enable multiple message threads management in the context of the Converged IP Messaging (CPM) service and in the context of CPM inter-working with SMS is provided. A CPM user can simply start a message-based conversation with another CPM or Short Message Service (SMS) user without explicitly establishing a session beforehand. All messages that belong to a given conversation are displayed in the corresponding conversational view (i.e. window) in the CPM user device, even if the conversation is stopped and restarted at a later time, and even if there are multiple message threads available (currently active or stored) in the CPM device. Message structures and behavior of the CPM system elements to enable the functionalities above as well as a mechanism makes the message threads management possible even between a CPM user and an SMS user are also provided.

In one embodiment of the present invention, a streaming multiprocessor (SM) uses a tree of nodes to manage threads. Each node specifies a set of active threads and a program counter. Upon encountering a conditional instruction that causes an execution path to diverge, the SM creates child nodes corresponding to each of the divergent execution paths. Based on the conditional instruction, the SM assigns each active thread included in the parent node to at most one child node, and the SM temporarily discontinues executing instructions specified by the parent node. Instead, the SM concurrently executes instructions specified by the child nodes. After all the divergent paths reconverge to the parent path, the SM resumes executing instructions specified by the parent node. Advantageously, the disclosed techniques enable the SM to execute divergent paths in parallel, thereby reducing undesirable program behavior associated with conventional techniques that serialize divergent paths across thread groups.

Methods and apparatus for dedicated thread management in a CMP having processing units, interface blocks, and function blocks interconnected by an on-chip network. In various embodiments, thread management occurs out-of-band allowing for fast, low-latency switching of threads without incurring the overhead associated with a software-based thread-management thread.

Thread switching prevents pipeline stalls when executing multiple threads. An analysis of a first thread identifies instructions capable of causing pipeline stalls. If pipeline stalls from the identified instructions are likely, thread switching instructions are added to the first thread in place of the identified instructions. Thread switching instructions direct a microprocessor to suspend executing the thread and begin executing a second thread. Thread switching instructions can be added to the second thread to enable the resumption of the first thread at the location specified by the identified instruction. The thread switching instructions are configured to avoid pipeline stalls when switching threads. Thread switching instructions can store and retrieve thread-specific information upon the suspension and resumption of threads. Thread switching instructions can schedule the execution of two or more threads in accordance with load balancing schemes. Threads can be modified using static or dynamic code analysis and modification techniques.

The invention provides a cloud-computing-based parking lot management system which comprises a vehicle information collecting subsystem, a thread management subsystem, a resource allocation subsystem, a cloud equipment subsystem, a mobile network interface subsystem and an automatic control subsystem. The could-computing-based parking lot management system can realize interaction with an intelligent cellphone client side, a cloud computing platform is taken as a processing architecture, a big data platform is taken as an information basis, resource distribution, data processing and request response are performed on the basis of service threads, efficient distribution and reasonable utilization of resources are realized by dividing static and dynamic service threads, own running laws of a parking lot are fully met, and high instantaneity requirements on service in the process of traveling can be met. The cloud-computing-based parking lot management system is supportive of a series of intelligent application scenes like parking space vacancy prediction inquiry, parking space optimized selection, incoming and outgoing path planning, vehicle collecting navigation and mobile payment of parking fee.

The invention discloses an automatic adjusting method and device for the thread number aiming to realizing the optimization of resource utilization. The automatic adjusting device comprises a resource monitoring module, a training module, a thread number determining module and a thread managing module, wherein the resource monitoring module is used for monitoring the use condition of each computing resource in a server; the training module is used for quantizing the resources used by one newly-increased thread for each type of task; the thread number determining module is used for determining the thread number of each type of task and giving a thread number adjustment instruction; the thread managing module is used for determining an instructive dynamic management thread of the module according to the thread number and is used for creating, recovering and destroying a thread. According to the automatic adjusting method and device disclosed by the invention, the adjustment on the thread number can be automatically finished by using methods of monitoring resources, managing the thread and the like, without manual intervention completely, so that the workload of optimizing performance by software developers is reduced, the thread number can be adjusted dynamically, accurately and quickly and the resource utilization of the server reaches or approaches to optimization.

The invention relates to a method for realizing kernel level process lib based on embedded Linux operating system, which realizes an integral kernel process manage system, provides kernel process management, signal amount management, memory management and log management, and AIP function interface of the function subgroup of standard C lib. The invention has the advantages that 1, the invention can modify little on kernel to support the software real-time or hardware real-time calling mechanism of prior embedded Linux operating system and confirm the application real-time demand, 2, the invention can completely eliminate the consumption of repeated switch of application process between user state and kernel state, to improve the integral performance of embedded Linux application system, 3, the invention shields the complexity of kernel module programming, to provide a development frame for developers and a series of programming interfaces (API), thereby reducing development and application complexity and improving development efficiency.

A thread manager makes a request to a resource manager for a hardware resource needed for execution of a thread representative of a function of a logical unit, the resource manager allocates the resource in response to the request, and the thread manager controls an execution state of the thread in accordance with a result of the allocation. The thread and resource managers conduct the request, the allocation and the control repeatedly in cooperation with each other until the execution of the thread reaches completion, thus achieving a simulation of the operation of the logical unit. Accordingly, through the operation simulation, it is possible to make the confirmation of the function and the evaluation of an architecture at an initial stage of the design of the logical unit, and further to cope flexibly with an alteration of the architecture by means of a minimum change of description.

A system for tracking memory dependencies includes a speculative thread management unit, which uses a bit vector to record and encode addresses of memory access. The speculative thread management unit includes a hashing unit that partitions the addresses into a load hash set and a store hash set, a load hash set unit for storing the load hash set, a store hash set unit for storing the store hash set, and a data dependence checking unit that checks data dependence when a thread completes, by comparing a load hash set of the thread to a store hash set of other threads.

A computer implemented method, an apparatus, and a computer usable program product for controlling startup request flooding. An application server instance is started. If the application server instance is throttled during a startup interval, a Web container thread manager is initiated. If the Web container thread manager identifies it is time to increment a Web container maximum thread pool size for the application server instance, the application server instance is notified to increment its Web container maximum thread pool size by a programmable amount. If the Web container maximum thread pool size for the application server instance has not reached a final maximum thread pool size, and if the startup interval for the application server instance has not completed, the Web container thread manager is suspended for an interval, after which the Web container thread manager identifies if it is time to increment the Web container maximum thread pool size for the application server instance.

The invention discloses a thread management method. The method comprises the following procedures: if a task processing request is received, determining a task included in the task processing request and the task type as well as the task ID of the task; judging whether a free thread matching the task type exists in a thread pool; if the free thread matching the task type does not exist in the thread pool, determining the priority weight of the task based on the task ID; when the priority weight is greater than a preset weight, building a new thread matching the task type in the thread pool and distributing the task to the newly built thread for processing. The invention also discloses a thread management device. According to the thread management method and device, the technical problem that the task with a high requirement on real-time performance is delayed for processing in the prior art is solved.

The invention discloses a multi-core parallel simulation engine system supporting joint operations. The system solves the problem that the real-time performance of a traditional joint operation system is easily influenced when step length is used to forward logic time. The system includes a model scheduling management module, a thread management module, an external interface management module and a high-level architecture (HLA) management module. According to the system, target nodes are assigned for simulation entities to enable total computation amounts of models on each node to be equivalent; then through the model scheduling management module, a scheduling schedule of each node is generated based on a principle of load balancing, the simulation step length is assigned for the models, and during a simulation process, the scheduling schedule is adjusted and the simulation step length of the destroyed entities and generated new entities is adjusted. The system can autonomously divide the scheduling schedule according to operating cycles of the models and the system step length, allow the entities to use the different physical models or the behavior models according to needs for simulation, and support real-time scheduling of large-scale simulation and the high-fidelity operation models.

A method and computer program product for defining a main email thread having a main thread distribution list defining one or more main email thread participants. One or more email messages may be associated with the main email thread. A sub email thread may be defined based upon, at least in part, the main email thread. The sub email thread may have a sub distribution list defining one or more sub email thread participants. The one or more sub email thread participants may include one or more of the main email thread participants. One or more email messages may be associated with the sub email thread.

A method and system for managing a thread pool of a plurality of first type threads and a plurality of second type threads in a computer system using a thread manager, specifically, a method for prioritizing, cancelling, balancing the work load between first type threads and second type threads, and avoiding deadlocks in the thread pool. A queue stores a first type task and a second type task, the second type task being executable by at least one of the plurality of second type threads. The availability of at least one of the plurality of first type threads is determined, and if none are available, the availability of at least one of the plurality of second type threads is determined. An available second type thread is selected to execute the first type task.

A system for discussion thread management using tag-based categorization, in which three types of tags are provided together to enable effective categorization of discussion threads, based on both automated and manual tagging. The three tag types are 1) user-defined tags, 2) moderator-promoted tags, and 3) system-generated tags. User-defined tags are arbitrarily defined by individual users and associated by users with posts to meet specific user needs. System-generated tags are automatically generated for each sub-thread to summarize a post and all the replies beneath it. System-generated tags can be promoted to a moderator-promoted tags when a moderator user verifies the correctness of a system-generated tag. The disclosed system detects topic changes in discussion threads based on the tags associated with each post in the thread. A moderator can manually examine sub-threads that have been determined to be off topic, and take appropriate actions. For example, a moderator may delete an off topic post or sub-thread, or fork a new thread of discussion for an off-topic sub-thread. Such processing of off-topic sub-threads can alternatively be made by the disclosed system automatically, without moderator intervention. Moderators can also define policies to control discussion moderation based on the disclosed tags and off-topic determinations.

Methods and apparatuses for thread management for multi-threading are described herein. In one embodiment, exemplary process includes selecting, during a compilation of code having one or more threads executable in a data processing system, a current thread having a most bottom order, determining resources allocated to one or more child threads spawned from the current thread, and allocating resources for the current thread in consideration of the resources allocated to the current thread's one or more child threads to avoid resource conflicts between the current thread and its one or more child threads. Other methods and apparatuses are also described.