search for: obj_offset

...nr_page; > > - if (!page) { > - VM_BUG_ON(obj_idx); > - return NULL; > - } > + offset = obj_idx * class->size; so we already know the `offset' before we call objidx_to_page_and_offset(), thus we can drop `struct size_class *class' and `obj_idx', and pass `long obj_offset' (which is `obj_idx * class->size') instead, right? we also _may be_ can return `cursor' from the function. static struct page *objidx_to_page_and_offset(struct page *first_page, unsigned long obj_offset, unsigned long *offset_in_page); this can save ~20 instructions, w...

...nr_page; > > - if (!page) { > - VM_BUG_ON(obj_idx); > - return NULL; > - } > + offset = obj_idx * class->size; so we already know the `offset' before we call objidx_to_page_and_offset(), thus we can drop `struct size_class *class' and `obj_idx', and pass `long obj_offset' (which is `obj_idx * class->size') instead, right? we also _may be_ can return `cursor' from the function. static struct page *objidx_to_page_and_offset(struct page *first_page, unsigned long obj_offset, unsigned long *offset_in_page); this can save ~20 instructions, w...

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and failed to fork easily. The problem was fragmentation caused by zram and GPU driver pages. Their pages cannot be migrated so compaction cannot work well, either so reclaimer ends up shrinking all of working set pages. It made system very slow and even to fail to fork easily.