From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Anton Vorontsov
<anton.vorontsov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: workqueue usage in vmpressure
Date: Wed, 10 Jul 2013 11:42:54 -0700 [thread overview]
Message-ID: <20130710184254.GA16979@mtj.dyndns.org> (raw)
Hello, guys.
While auditing cgroup_subsys_state() usages, I noticed something weird
in vmpressure. vmpressure() schedules vmpr->work where vmpr is
embedded in mem_cgroup but I can't find where it's flushed / canceled?
What prevents the memcg going away while the work item is pending or
in flight?
Thanks.
--
tejun
next reply other threads:[~2013-07-10 18:42 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 18:42 Tejun Heo [this message]
[not found] ` <20130710184254.GA16979-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-07-11 8:31 ` workqueue usage in vmpressure Michal Hocko
[not found] ` <20130711083110.GC21667-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-07-11 8:43 ` Li Zefan
[not found] ` <51DE701C.6010800-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2013-07-11 9:25 ` Michal Hocko
[not found] ` <20130711092542.GD21667-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-07-11 9:28 ` Li Zefan
2013-07-11 9:33 ` [PATCH v2] vmpressure: make sure memcg stays alive until all users are signaled Michal Hocko
2013-07-11 9:33 ` Michal Hocko
2013-07-11 15:44 ` Tejun Heo
2013-07-11 16:22 ` Michal Hocko
2013-07-11 16:22 ` Michal Hocko
2013-07-11 16:32 ` Tejun Heo
2013-07-12 8:40 ` Michal Hocko
2013-07-12 9:20 ` Li Zefan
2013-07-12 9:20 ` Li Zefan
2013-07-12 9:29 ` Michal Hocko
2013-07-12 9:29 ` Michal Hocko
2013-07-12 9:54 ` Li Zefan
2013-07-12 9:54 ` Li Zefan
2013-07-12 10:37 ` Michal Hocko
2013-07-15 3:07 ` Li Zefan
2013-07-15 3:07 ` Li Zefan
2013-07-15 9:20 ` Michal Hocko
2013-07-15 9:53 ` Li Zefan
2013-07-15 9:53 ` Li Zefan
2013-07-12 9:24 ` [PATCH 1/3] vmpressure: document why css_get/put is not necessary for work queue based signaling Michal Hocko
2013-07-12 9:24 ` [PATCH 2/3] vmpressure: change vmpressure::sr_lock to spinlock Michal Hocko
2013-07-12 9:24 ` [PATCH 3/3] vmpressure: do not check for pending work to prevent from new work Michal Hocko
2013-07-12 9:24 ` Michal Hocko
2013-07-12 18:48 ` [PATCH 1/3] vmpressure: document why css_get/put is not necessary for work queue based signaling Tejun Heo
2013-07-15 10:27 ` Michal Hocko
2013-07-15 10:27 ` Michal Hocko
2013-07-12 18:34 ` [PATCH v2] vmpressure: make sure memcg stays alive until all users are signaled Tejun Heo
2013-07-12 18:40 ` Tejun Heo
2013-07-12 6:03 ` Li Zefan
2013-07-12 6:03 ` Li Zefan
2013-07-15 10:30 ` [PATCH v3 1/3] vmpressure: change vmpressure::sr_lock to spinlock Michal Hocko
2013-07-15 10:30 ` Michal Hocko
2013-07-15 10:30 ` [PATCH v3 2/3] vmpressure: do not check for pending work to prevent from new work Michal Hocko
2013-07-15 10:30 ` [PATCH v3 3/3] vmpressure: Make sure there are no events queued after memcg is offlined Michal Hocko
2013-07-11 8:45 ` workqueue usage in vmpressure Li Zefan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130710184254.GA16979@mtj.dyndns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=anton.vorontsov-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.