Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+V2\]\s+xfs\:\s+introduce\s+CONFIG_XFS

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+V2\]\s+xfs\:\s+introduce\s+CONFIG_XFS_WARN\s*$/: 8 ]

Total 8 documents matching your query.

1. [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 24 Apr 2013 18:55:46 +1000; Running a CONFIG_XFS_DEBUG kernel in production environments is not the best idea as it introduces significant overhead, can change the behaviour of algorithms (such as allocation) to improve test co; /archives/xfs/2013-04/msg00536.html (19,879 bytes)
2. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Chandra Seetharaman <sekharan@xxxxxxxxxx>; Date: Wed, 24 Apr 2013 13:39:52 -0500; Hi Dave, Since this solution is for production environment, would it be valuable to have a sysctl variable to allow enabling/disabling XFS_WARN, as opposed to needing to recompile the module afresh ?; /archives/xfs/2013-04/msg00547.html (25,337 bytes)
3. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Thu, 25 Apr 2013 08:58:21 +1000; The idea is that distros enable it on the debug kernel packages rather than using CONFIG_XFS_DEBUG=y. Hence if someone has a problem, they just install the debug kernel and they get all this addition; /archives/xfs/2013-04/msg00551.html (9,848 bytes)
4. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Wed, 24 Apr 2013 19:21:17 -0500; I agree. kernel-debug, or whatever your distro does similarly, is the right use for this code. -Eric; /archives/xfs/2013-04/msg00552.html (10,650 bytes)
5. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Chandra Seetharaman <sekharan@xxxxxxxxxx>; Date: Thu, 25 Apr 2013 09:07:49 -0500; Thanks for the clarification. I was thinking that CONFIG_XFS_DEBUG would be enabled in the distro's debug kernel and this new option is in addition to that. Hence, my question. So, with this new conf; /archives/xfs/2013-04/msg00558.html (11,769 bytes)
6. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Brian Foster <bfoster@xxxxxxxxxx>; Date: Thu, 25 Apr 2013 10:48:27 -0400; Looks good. Reviewed-by: Brian Foster <bfoster@xxxxxxxxxx>; /archives/xfs/2013-04/msg00561.html (25,044 bytes)
7. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Fri, 26 Apr 2013 07:44:05 +1000; If you are shipping a debug kernel with CONFIG_XFS_DEBUG, then you don't want your customers running that debug kernel for very long. CONFIG_XFS_DEBUG changes allocation algorithms to improve test co; /archives/xfs/2013-04/msg00582.html (11,411 bytes)
8. Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN (score: 1): Author: Chandra Seetharaman <sekharan@xxxxxxxxxx>; Date: Thu, 25 Apr 2013 17:29:58 -0500; Thanks Dave.; /archives/xfs/2013-04/msg00583.html (12,077 bytes)

Current List: 1 - 8
Page: [1]