commit-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[SCM] Hurd branch, master, updated. 7f0e0da1fb514c30df296e22481761b77f6d


From: Samuel Thibault
Subject: [SCM] Hurd branch, master, updated. 7f0e0da1fb514c30df296e22481761b77f6d3a6a
Date: Mon, 03 Oct 2011 20:33:20 +0000

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Hurd".

The branch, master has been updated
       via  7f0e0da1fb514c30df296e22481761b77f6d3a6a (commit)
      from  2f8e829bdc2e868d1872e21b4acae404a2316e68 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 7f0e0da1fb514c30df296e22481761b77f6d3a6a
Author: Sergio López <address@hidden>
Date:   Thu Sep 29 11:44:40 2011 +0200

    Sync pager before clearing MAY_CACHE flag
    
    Clearing MAY_CACHE flag on a pager initiates a memory object
    termination if this one is not referenced anymore. If the object has a
    significant number of dirty pages (i.e. a file recently created was
    unlinked before diskfs periodical sync) this operation generates a lot
    of stress on the translator. This is one of the most common sources
    for thread storms.
    
    Sync'ing the pager before clearing that flag ensures that there aren't
    dirty pages in the object before its termination.
    
    * ext2fs/pager.c (drop_pager_softrefs): Sync pager before clearing
    MAY_CACHE flag.

-----------------------------------------------------------------------

Summary of changes:
 ext2fs/pager.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
Hurd



reply via email to

[Prev in Thread] Current Thread [Next in Thread]