On Tue, 19 Nov 2013, [email protected] wrote: > Subject: [to-be-updated] > mm-memcg-add-memoryoom_control-notification-for-system-oom.patch removed from > -mm tree > To: > [email protected],[email protected],[email protected],[email protected],[email protected] > From: [email protected] > Date: Tue, 19 Nov 2013 13:38:14 -0800 > > > The patch titled > Subject: mm, memcg: add memory.oom_control notification for system oom > has been removed from the -mm tree. Its filename was > mm-memcg-add-memoryoom_control-notification-for-system-oom.patch > > This patch was dropped because an updated version will be merged
Why is this removed? I've laid out my perspective for doing userspace oom handling and this is a vital part for system oom handling. I know that we are currently discussing alternative proposals but my proposal is by far the most complete and allows the most powerful policies to be implemented in userspace. I'd prefer if we would keep the patch unless an actual alternative is proposed and agreed upon, we can still discuss alternatives while this in -mm and this patch in no way precludes other mechanisms from being implemented. So why remove this? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
