Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1203975 > unrolled thread
| Started by | Vlastimil Babka <vbabka@suse.cz> |
|---|---|
| First post | 2015-08-10 12:00 +0200 |
| Last post | 2015-08-10 12:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC v3 2/2] mm, compaction: make kcompactd rely on sysctl_extfrag_threshold Vlastimil Babka <vbabka@suse.cz> - 2015-08-10 12:00 +0200
| From | Vlastimil Babka <vbabka@suse.cz> |
|---|---|
| Date | 2015-08-10 12:00 +0200 |
| Subject | Re: [RFC v3 2/2] mm, compaction: make kcompactd rely on sysctl_extfrag_threshold |
| Message-ID | <pVS29-2wD-83@gated-at.bofh.it> |
On 08/09/2015 07:21 PM, PINTU KUMAR wrote: >> >> -extern int fragmentation_index(struct zone *zone, unsigned int order); >> +extern int fragmentation_index(struct zone *zone, unsigned int order, > >> + bool ignore_suitable); > > We would like to retain the original fragmentation_index as it is. > Because in some cases people may be using it without kcompactd. > In such cases, future kernel upgrades will suffer. > In my opinion fragmentation_index should work just based on zones and order. I don't understand the concern. If you pass 'false' to ignore_suitable, you get the standard behavior. Only kcompactd uses the altered behavior. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web