On Wed, Apr 2, 2008 at 10:58 AM, KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> wrote: > Hi > > > > > hmm, > > > I can't find it from mailing list log. > > > Could you recall subject of that patch? > > > > here is the URL http://lkml.org/lkml/2006/8/4/77 > > Oh! thanks. > but, this patch only get per process # of swap pages. > > and the following patch is merged -mm before a while. > http://marc.info/?l=linux-kernel&m=120654533828554&w=2 > > thus, now we have its capability via /proc/pid/smap. > > in my understanding, originally requirement wanted following tuple. > > - destination begin offset / size > - source begin offset / size > - process/task > > ah...yes...exactly. but Mulyadi patch is good headstart for me to focus on - to see how it can be tweaked for extracting out this lean information. lean because as compared with blktrace, it is just focusing on the BOUNDARY of the swapspace being written or read (whereas blktrace will include the data itself).....every seconds or every minutes, snapshot of these kind of information will allow us to see how the swapspace is dynamically being used....and then we can then design a good page replacement policy or swapspace usage algorithm.....eg, to maximize the clustering factor when paging. sort of a simulation tool...... -- Regards, Peter Teoh -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
