All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhouping Liu <zliu@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] mem/oom: fixed a cpuset error
Date: Sat, 27 Apr 2013 02:34:49 -0400 (EDT)	[thread overview]
Message-ID: <1655733918.3290321.1367044489461.JavaMail.root@redhat.com> (raw)
In-Reply-To: <201304270204.34020.vapier@gentoo.org>



----- Original Message -----
> From: "Mike Frysinger" <vapier@gentoo.org>
> To: ltp-list@lists.sourceforge.net
> Cc: "Zhouping Liu" <zliu@redhat.com>
> Sent: Saturday, April 27, 2013 2:04:32 PM
> Subject: Re: [LTP] [PATCH v2] mem/oom: fixed a cpuset error
> 
> On Saturday 27 April 2013 00:23:14 Zhouping Liu wrote:
> > The reason is that node0 only contains all CPUs, no any memory,
> 
> no any memory -> no memory

OK.

> 
> > and node1 contains all memory, but no CPUs, in the previous codes,
> 
> change "CPUs, in" to "CPUs. In"

OK.

> 
> > we only do cpuset testing on a independent node, which caused the
> 
> a -> an

OK.

> 
> > sub-cpuset cgroup only contains CPUs or memory in one node, but
> 
> only contains -> to only contain

why 'contain', I think it should be 'contains', isn't it?

> 
> > that's not permitted in the special machine. The patch fixed it.
> 
> what is a "special machine" ?

the special machine is that it has such nodes(describe above),
in which there's only CPUs or memory.

how about this:

"that's not permitted in the such above special machine."

> 
> also, generally there's no need to say "The patch fixed it".  the fact that
> you've described a bug and have a patch implies that this fixes things.
> 
> > +		tst_resm(TINFO, "None CPUs in the node%ld", nd);
> 
> i think you mean "no" instead of "None"
> 
> > +		tst_resm(TINFO, "Only use CPU0 in the cpuset cgroup "
> > +				"for the special scenario");
> 
> what is "the special scenario" ?

the special scenario is "no CPUs in the node%ld", I think it's clear in log message.

> 
> >  	mount_mem("cpuset", "cpuset", NULL, CPATH, CPATH_NEW);
> > -	if (is_numa(cleanup) > 0)
> > -		/* For NUMA system, using the first node for cpuset.mems */
> > -		write_cpusets(get_a_numa_node(cleanup));
> > -	else
> > -		/* For nonNUMA system, using node0 for cpuset.mems */
> > -		write_cpusets(0);
> > +
> > +	/*
> > +	 * Not any nodes contain memory, so using get_allowed_nodes(NH_MEMS)
> 
> "Not any" -> "No"

it's not that meaning, what I meant here is that there's not any nodes contain
memory in a NUMA system, Some nodes contain memory, but some nodes don't.

> 
> "using" -> "use"

OK.

> 
> > +	 * to get a memory node, the operation also applies to Non-NUMA
> 
> change the ", the" to ". This".

OK

> 
> > +	 * system.
> 
> systems.
> 
> > +        /*
> 
> looks like you mixed spaces & tabs.  only use tabs.

OK.

> 
> > +	 * Not any nodes contain memory, so using get_allowed_nodes(NH_MEMS)
> > +	 * to get a memory node, the operation also applies to Non-NUMA
> > +	 * system.
> 
> same comments about the grammar here as above
> -mike
> 

-- 
Thanks,
Zhouping

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2013-04-27  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-27  4:23 [LTP] [PATCH v2] mem/oom: fixed a cpuset error Zhouping Liu
2013-04-27  6:04 ` Mike Frysinger
2013-04-27  6:34   ` Zhouping Liu [this message]
2013-04-29  0:08     ` Mike Frysinger
2013-04-29  6:12       ` Zhouping Liu

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=1655733918.3290321.1367044489461.JavaMail.root@redhat.com \
    --to=zliu@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.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.