Hi! > > > Use readahead() syscall and check if subsequent > > > read saves some I/O and if cache size increased. > > > > > > Signed-off-by: Jan Stancek <[email protected]> > > > --- > > > testcases/kernel/syscalls/readahead/readahead02.c | 371 > > > +++++++++++++++++++++ > > > 1 files changed, 371 insertions(+), 0 deletions(-) > > > create mode 100644 > > > testcases/kernel/syscalls/readahead/readahead02.c > > > > > > > I'm thinking if we should write some common codes to fetch certain > > fields from /proc/meminfo and if we should move read/write > > /sys/kernel/vm files to libkerntest... We do have some duplicated > > functions in mm tests. > > Sounds reasonable, I also noticed seeing (and using) some snippets > over and over again.
I'm plannig (for some time) to write scanf and printf like functions to do exactly that, just haven't had time to write them. -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
