> >> so MAX_SWAPFILES is not 30 anymore, it's 29. While LTP defines > >> MAX_SWAPFILES > >> to 30 in include/swaponoff.h(hmmm....hardcode, I don't think it's a good > >> idea :-|). > >> > >> So the way to solve(maybe) the problem is clear: change MAX_SWAPFILES > >> to 29 when CONFIG_MEMORY_FAILURE is enabled. My question is: is there > >> a good way to check whether a kernel option is enabled or not? I searched > >> in the old discussions in this maillist and found nothing. I want to know > >> if > >> > >> the developers have some new ideas? > >> > > > > I've seen 28 as the MAX as well, it all depends on the config options. > > I've been looking at re-architecting the test to do some sort of repeat > > test to the max number of successful swap creations and then verifying that > > the same number is reachable at least 2 times. MAX_SWAPFILES is never > > exported to userspace. It's a compile time #define that depends on the > > kernel config options. > > What about /proc/config.gz (or something similar)? Seems like a > simple enough thing to check for absolute clarity... don't remember > the kernel option for that though.
As far as I know this option is disabled at least for debian see: http://wiki.debian.org/KernelFAQ So this would lead to state where the test looks for config in different locations and this is IMHO too fragile to maintain. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
