会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Pre-fetching of pages prior to a hard page fault sequence
    • 在硬页错误序列之前预取页面
    • US06317818B1
    • 2001-11-13
    • US09282499
    • 1999-03-30
    • Arthur ZwiegincewJames E. Walsh
    • Arthur ZwiegincewJames E. Walsh
    • G06F1200
    • G06F12/08G06F2212/401
    • Hard page fault patterns of an application program module are analyzed in order to determine the pages that will be retrieved from disk storage during a common hard page fault scenario. Copies of, or references to, the determined pages are stored in a scenario file, along with an index referred to as a page sequence. The scenario file may also include a prologue indicating events that lead to a hard page fault scenario and an epilogue that may indicate subsequent hard page fault scenarios. Execution of the application program module is monitored to detect the occurrence of a hard page fault scenario. When a hard page fault scenario is detected, a corresponding scenario file is fetched from disk storage and the determined pages, or copies thereof, are transferred into RAM. The determined pages, or copies thereof, may be placed on a stand-by list in RAM and later soft-faulted into the working set of the application program upon request by the application program module, thereby avoiding a sequence of hard page faults.
    • 分析应用程序模块的硬页错误模式,以确定在常见硬页错误情况下将从磁盘存储器检索的页面。 将确定的页面的副本或引用存储在脚本文件中,以及被称为页面序列的索引。 场景文件还可以包括指示导致硬页错误情况的事件的序言,以及可指示后续硬页错误情景的结尾语。 监控应用程序模块的执行情况,以检测硬页错误情况的发生。 当检测到硬页面故障场景时,从磁盘存储器取出相应的场景文件,并将确定的页面或其副本传送到RAM中。 确定的页面或其副本可以被放置在RAM中的备用列表上,并且随后由应用程序模块请求而被软错误地发送到应用程序的工作集合中,从而避免了一系列的硬页错误。
    • 2. 发明授权
    • Pre-fetching of pages prior to a hard page fault sequence
    • 在硬页错误序列之前预取页面
    • US06633968B2
    • 2003-10-14
    • US09794851
    • 2001-02-27
    • Arthur ZwiegincewJames E. Walsh
    • Arthur ZwiegincewJames E. Walsh
    • G06F1200
    • G06F12/08G06F2212/401
    • A method for pre-fetching of pages prior to a hard page fault sequence is described. A scenario file comprising a list of pages that need to be pre-fetched may be created. A scenario that requires pre-fetching may be automatically detected when process creation begins (such as at application startup or system boot). The scenario begins and it is determined whether or not a scenario file exists for the scenario. If not, the process continues (for example, the application is started up and run, the system is booted, etc.). If a scenario file does exist, the pages in the scenario file are pre-fetched to RAM. The process continues (application is started up and run, the system is booted, etc.). Pages that are used by the application are logged into a scenario log. The scenario log is also used to log page faults. An end scenario timer is started and it is determined whether a page fault (soft or hard) has been detected. Page faults are logged into memory (the scenario log) and the end scenario timer is reset each time a new page fault is encountered. If the end scenario timer has reached a predetermined threshold, the scenario ends and a work item is queued to post-process the scenario log and scenario file during idle time. The scenario file and scenario log are processed and an updated scenario file is written out to the disk space.
    • 描述了在硬页错误序列之前预取页的方法。 可以创建包括需要预取的页面列表的场景文件。 当进程创建开始时(例如在应用程序启动或系统启动时),可能会自动检测到需要预取的场景。 场景开始,确定场景文件是否存在。 如果没有,则该过程继续(例如,应用程序启动并运行,系统启动等)。 如果场景文件存在,则场景文件中的页面将预取到RAM。 该过程继续(应用程序启动并运行,系统启动等)。 应用程序使用的页面将记录到方案日志中。 方案日志也用于记录页面错误。 启动结束场景定时器,确定是否检测到页面错误(软或硬)。 页面错误将记录到内存(方案日志)中,并且每次遇到新的页面错误时,将重新设置结束方案定时器。 如果结束情景定时器已经达到预定阈值,则该方案结束并且工作项排队等待以在空闲时间期间对方案日志和方案文件进行后处理。 处理方案文件和方案日志,并将更新的方案文件写入磁盘空间。