search for: compaction

Dear R-developers, I would like to suggest a 'method' slot for format.ftable() (see an adjusted 'format.ftable()' below, taken from the source of R-2.15.2). At the moment, format.ftable() contains several empty cells due to the way the row and column labels are printed. This creates problems (= unwanted empty columns/rows) when converting an ftable to a LaTeX table; see an

...e 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing >> and 20~30 memory is reserved for zram. >> >> I found that many pages of GPU driver and zram are non-movable pages. So I >> reported Minchan Kim, the maintainer of zram, and he made the internal >> compaction logic of zram. And I made the internal compaction of GPU driver. >> >> They reduced some fragmentation but they are not enough effective. >> They are activated by its own interface, /sys, so they are not cooperative >> with kernel compaction. If there is too much fragmentati...

...e 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing >> and 20~30 memory is reserved for zram. >> >> I found that many pages of GPU driver and zram are non-movable pages. So I >> reported Minchan Kim, the maintainer of zram, and he made the internal >> compaction logic of zram. And I made the internal compaction of GPU driver. >> >> They reduced some fragmentation but they are not enough effective. >> They are activated by its own interface, /sys, so they are not cooperative >> with kernel compaction. If there is too much fragmentati...

...nsumed for graphic processing >>>> and 20~30 memory is reserved for zram. >>>> >>>> I found that many pages of GPU driver and zram are non-movable pages. So I >>>> reported Minchan Kim, the maintainer of zram, and he made the internal >>>> compaction logic of zram. And I made the internal compaction of GPU driver. >>>> >>>> They reduced some fragmentation but they are not enough effective. >>>> They are activated by its own interface, /sys, so they are not cooperative >>>> with kernel compaction....

...nsumed for graphic processing >>>> and 20~30 memory is reserved for zram. >>>> >>>> I found that many pages of GPU driver and zram are non-movable pages. So I >>>> reported Minchan Kim, the maintainer of zram, and he made the internal >>>> compaction logic of zram. And I made the internal compaction of GPU driver. >>>> >>>> They reduced some fragmentation but they are not enough effective. >>>> They are activated by its own interface, /sys, so they are not cooperative >>>> with kernel compaction....

...bounds doclen not within bounds doclen not within bounds doclen not within bounds doclen not within bounds doclen not within bounds doclen not within bounds [repeated 52498 times] OTOH, notmuch compact completes for me, so that might be unrelated. I'm copying the Xapian list for input. > Compaction failed: A Xapian exception occurred > > Running xapian-check says: > > docdata: > blocksize=8K items=2677 firstunused=19 revision=15425 levels=1 root=17 > B-tree checked okay > docdata table structure checked OK > > termlist: > blocksize=8K items=2986940 firstunused=27...

...ub.com/0day-ci/linux/commits/Minchan-Kim/Support-non-lru-page-migration/20160311-153649 config: x86_64-nfsroot (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): In file included from mm/compaction.c:12:0: >> include/linux/compaction.h:87:20: error: static declaration of 'isolate_movable_page' follows non-static declaration static inline bool isolate_movable_page(struct page *page, isolate_mode_t mode) ^ In file included from mm/compaction.c:11:0:...

...ub.com/0day-ci/linux/commits/Minchan-Kim/Support-non-lru-page-migration/20160311-153649 config: x86_64-nfsroot (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): In file included from mm/compaction.c:12:0: >> include/linux/compaction.h:87:20: error: static declaration of 'isolate_movable_page' follows non-static declaration static inline bool isolate_movable_page(struct page *page, isolate_mode_t mode) ^ In file included from mm/compaction.c:11:0:...

Compaction calls interfaces of driver page migration instead of calling balloon migration directly. Signed-off-by: Gioh Kim <gioh.kim at lge.com> --- drivers/virtio/virtio_balloon.c | 1 + mm/compaction.c | 9 +++++---- mm/migrate.c | 21 ++++++++++++--------- 3 fi...

On Fri, Jun 26, 2015 at 12:58 PM, Gioh Kim <gioh.kim at lge.com> wrote: > Compaction calls interfaces of driver page migration > instead of calling balloon migration directly. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 1 + > mm/compaction.c | 9 +++++---- > mm/migrate.c...

On Fri, Jun 26, 2015 at 12:58 PM, Gioh Kim <gioh.kim at lge.com> wrote: > Compaction calls interfaces of driver page migration > instead of calling balloon migration directly. > > Signed-off-by: Gioh Kim <gioh.kim at lge.com> > --- > drivers/virtio/virtio_balloon.c | 1 + > mm/compaction.c | 9 +++++---- > mm/migrate.c...

...ferent functions, one that iterates, and one that uses compact. The advantage of compact - it runs approximately 8 times as fast (we are CPU limited in each case - writing to tmpfs first, then rsyncing to the destination) and it takes approximately 75% of the space of a fresh database with maximum compaction. The downside of compact - can't delete things (or at least I can't see how). Does anyone have any suggestions for a better way to do this? I'll paste the code for the two different functions below (Cyrus is written in C - hence the C-compatible API interface). I would prefer not to...

Dear expeRts, Please find attached the .diff for a bug fix in R-devel 62124. format.ftable() fails to format ftable()s correctly which have no row.vars or no col.vars. That should work with the patch (the example code below also runs correctly for all the (new) 'method's). Cheers, Marius --8<---------------cut here---------------start------------->8--- (ft1 <- ftable(Titanic,

> .Internal(inspect(1:10)) @300e4e8 13 INTSXP g0c0 [NAM(3)] 1 : 10 (compact) > .Internal(inspect(seq(1,10))) @3b6e1f8 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... > system.time(1:1e7) user system elapsed 0 0 0 > system.time(seq(1,1e7)) user system elapsed 0.05 0.00 0.04 It seems that result of function 'seq' doesn't use compact

...0% memory is consumed for graphic processing > >> and 20~30 memory is reserved for zram. > >> > >> I found that many pages of GPU driver and zram are non-movable pages. So I > >> reported Minchan Kim, the maintainer of zram, and he made the internal > >> compaction logic of zram. And I made the internal compaction of GPU driver. > >> > >> They reduced some fragmentation but they are not enough effective. > >> They are activated by its own interface, /sys, so they are not cooperative > >> with kernel compaction. If there is...

...3 page allocation failed. It has memory size 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing and 20~30 memory is reserved for zram. I found that many pages of GPU driver and zram are non-movable pages. So I reported Minchan Kim, the maintainer of zram, and he made the internal compaction logic of zram. And I made the internal compaction of GPU driver. They reduced some fragmentation but they are not enough effective. They are activated by its own interface, /sys, so they are not cooperative with kernel compaction. If there is too much fragmentation and kernel starts to compaction,...

...3 page allocation failed. It has memory size 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing and 20~30 memory is reserved for zram. I found that many pages of GPU driver and zram are non-movable pages. So I reported Minchan Kim, the maintainer of zram, and he made the internal compaction logic of zram. And I made the internal compaction of GPU driver. They reduced some fragmentation but they are not enough effective. They are activated by its own interface, /sys, so they are not cooperative with kernel compaction. If there is too much fragmentation and kernel starts to compaction,...

...3 page allocation failed. It has memory size 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing and 20~30 memory is reserved for zram. I found that many pages of GPU driver and zram are non-movable pages. So I reported Minchan Kim, the maintainer of zram, and he made the internal compaction logic of zram. And I made the internal compaction of GPU driver. They reduced some fragmentation but they are not enough effective. They are activated by its own interface, /sys, so they are not cooperative with kernel compaction. If there is too much fragmentation and kernel starts to compaction,...

...3 page allocation failed. It has memory size 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing and 20~30 memory is reserved for zram. I found that many pages of GPU driver and zram are non-movable pages. So I reported Minchan Kim, the maintainer of zram, and he made the internal compaction logic of zram. And I made the internal compaction of GPU driver. They reduced some fragmentation but they are not enough effective. They are activated by its own interface, /sys, so they are not cooperative with kernel compaction. If there is too much fragmentation and kernel starts to compaction,...

I am fairly confident that these issues are related to killing the scriptindex process ungracefully causing blocks that were queued for writing to disk to not get written. I mention to send you the file because it could be that you would see almost immediately with the situation is. Thanks > ----- Original Message ----- > From: oscaruser@programmer.net > To: