Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+xfs\:\s+mark\s+the\s+xfssyncd\s+workqueue\s+as\s+non\-reentrant\s*$/: 3 ]

Total 3 documents matching your query.

1. [PATCH] xfs: mark the xfssyncd workqueue as non-reentrant (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 5 Dec 2011 03:53:21 -0500
On a system with lots of memory pressure that is stuck on synchronous inode reclaim the workqueue code will run one instance of the inode reclaim work item on every CPU. which is not what we want. Ma
/archives/xfs/2011-12/msg00080.html (7,945 bytes)

2. Re: [PATCH] xfs: mark the xfssyncd workqueue as non-reentrant (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 19 Dec 2011 11:02:27 +1100
Ok, I've had a look in detail at what the WQ_NON_REENTRANT flag does and I agree that this is the correct behaviour for the xfssyncd - only one instance per filesystem should run at any given time. R
/archives/xfs/2011-12/msg00358.html (8,143 bytes)

3. Re: [PATCH] xfs: mark the xfssyncd workqueue as non-reentrant (score: 1)
Author: Ben Myers <bpm@xxxxxxx>
Date: Tue, 20 Dec 2011 10:45:07 -0600
FWICS this seems reasonable... Reviewed-by: Ben Myers <bpm@xxxxxxx>
/archives/xfs/2011-12/msg00367.html (8,744 bytes)


This search system is powered by Namazu