cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Serge Hallyn
	<serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] cgroup: don't show pid list on tasks/procs in ascending order
Date: Wed, 16 Jan 2013 09:50:35 +0800	[thread overview]
Message-ID: <50F6076B.8080704@oracle.com> (raw)
In-Reply-To: <20130115154332.GA2598-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>

Hi Serge and Tejun,
On 01/15/2013 11:43 PM, Tejun Heo wrote:
> Hello, guys.
> 
> On Tue, Jan 15, 2013 at 08:08:11AM -0600, Serge Hallyn wrote:
>>> I did this for two reasons, one is for the documents, another is per
>>> Cgroup TODO list from Tejun -- https://lkml.org/lkml/2012/9/13/542
>>>
>>> . Misc issues
>>>
>>>   * Sort & unique when listing tasks.  Even the documentation says it
>>>     doesn't happen but we have a good hunk of code doing it in
>>>     cgroup.c.  I'm gonna rip it out at some point.  Again, if you
>>>     don't like it, scream.
>>
>> Yeah, I figured, and since he also wants to move to a place where
>> cgroups are always manipulated using a library, not by hand, it
>> would make sense to get rid of the overhead there.  I just don't
>> really like either one of those :)  And in the list of things to
>> clean up in cgroups, this seems like one that can wait.
> 
> I want it gone but last time I pinged there were some people depending
> on it, so I don't think I can.  I think we'll have to put it on ice
> for now at least.  :(
Thanks both of you for the response :)  So I'll put it aside for now.

Regards,
-Jeff

      parent reply	other threads:[~2013-01-16  1:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15  5:28 [PATCH] cgroup: don't show pid list on tasks/procs in ascending order Jeff Liu
     [not found] ` <50F4E902.20202-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-01-15  6:23   ` Jeff Liu
2013-01-15  6:25   ` Serge Hallyn
2013-01-15  6:30     ` Jeff Liu
     [not found]       ` <50F4F76D.2050409-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-01-15  6:34         ` Serge Hallyn
2013-01-15  6:56           ` Jeff Liu
     [not found]             ` <50F4FD99.7070406-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2013-01-15 14:08               ` Serge Hallyn
2013-01-15 15:43                 ` Tejun Heo
     [not found]                   ` <20130115154332.GA2598-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-01-15 16:14                     ` Serge E. Hallyn
     [not found]                       ` <20130115161420.GA6885-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2013-01-15 16:17                         ` Tejun Heo
2013-01-16  1:50                     ` Jeff Liu [this message]

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=50F6076B.8080704@oracle.com \
    --to=jeff.liu-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).