From: Ingo Molnar <mingo@kernel.org>
To: Waiman Long <longman@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org,
changbin.du@intel.com, jstancek@redhat.com,
akpm@linux-foundation.org, borntraeger@de.ibm.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/debugobjects] debugobjects: Reduce contention on the global pool_lock
Date: Mon, 6 Feb 2017 23:50:25 +0100 [thread overview]
Message-ID: <20170206225025.GA27182@gmail.com> (raw)
In-Reply-To: <7cc1ba2c-b8f3-3f64-f093-0b5600f676e1@redhat.com>
* Waiman Long <longman@redhat.com> wrote:
> On 02/05/2017 05:03 AM, Ingo Molnar wrote:
> > * tip-bot for Waiman Long <tipbot@zytor.com> wrote:
> >
> >> ---
> >> lib/debugobjects.c | 31 ++++++++++++++++++++++---------
> >> 1 file changed, 22 insertions(+), 9 deletions(-)
> >>
> >> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
> >> index dc78217..5476bbe 100644
> >> --- a/lib/debugobjects.c
> >> +++ b/lib/debugobjects.c
> >> @@ -172,25 +172,38 @@ alloc_object(void *addr, struct debug_bucket *b, struct debug_obj_descr *descr)
> >>
> >> /*
> >> * workqueue function to free objects.
> >> + *
> >> + * To reduce contention on the global pool_lock, the actual freeing of
> >> + * debug objects will be delayed if the pool_lock is busy. We also free
> >> + * the objects in a batch of 4 for each lock/unlock cycle.
> >> */
> >> +#define ODEBUG_FREE_BATCH 4
> >> static void free_obj_work(struct work_struct *work)
> >> {
> > Please put an extra newline before function definitions.
> >
> > Looks good otherwise!
> >
> > Thanks,
> >
> > Ingo
>
>
> Sure, I can do that. BTW the debugobjects patch was also pull into the
> -mm tree a little while ago. Will that be a problem?
Should not be a problem usually, Andrew typically drops such patches if they show
up in a maintainer tree via linux-next.
And once accepted we don't silently drop patches from -tip hosted maintainer
trees, so this is a reliable workflow.
Thanks,
Ingo
next prev parent reply other threads:[~2017-02-06 22:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 20:17 [RESEND PATCH v2 0/3] debugobjects: Reduce global pool_lock contention Waiman Long
2017-01-05 20:17 ` [RESEND PATCH v2 1/3] debugobjects: Track number of kmem_cache_alloc/kmem_cache_free done Waiman Long
2017-02-04 16:22 ` [tip:core/debugobjects] " tip-bot for Waiman Long
2017-02-05 10:08 ` Ingo Molnar
2017-01-05 20:17 ` [RESEND PATCH v2 2/3] debugobjects: Scale thresholds with # of CPUs Waiman Long
2017-02-04 16:23 ` [tip:core/debugobjects] " tip-bot for Waiman Long
2017-01-05 20:17 ` [RESEND PATCH v2 3/3] debugobjects: Reduce contention on the global pool_lock Waiman Long
2017-02-04 16:23 ` [tip:core/debugobjects] " tip-bot for Waiman Long
2017-02-05 10:03 ` Ingo Molnar
2017-02-06 22:09 ` Waiman Long
2017-02-06 22:50 ` Ingo Molnar [this message]
2017-02-05 16:13 ` tip-bot for Waiman Long
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=20170206225025.GA27182@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=changbin.du@intel.com \
--cc=hpa@zytor.com \
--cc=jstancek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=longman@redhat.com \
--cc=tglx@linutronix.de \
/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).