linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mikhail.v.gavrilov@gmail.com
Cc: mhocko@kernel.org, darrick.wong@oracle.com,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Google Chrome cause locks held in system (kernel 4.15 rc2)
Date: Sun, 7 Jan 2018 12:42:40 +0900	[thread overview]
Message-ID: <201801071242.CCD05710.HFFVQJMtOOFOSL@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1515259453.17396.17.camel@gmail.com>

mikhail wrote:
> Thanks, I investigated the code of new version udplogger. I understood
> why it is not subject to the problems described above. Because it uses
> one file for all clients. The old version tried to create a separate
> file for each client.
> 
> Why you not using git hosting?

Because I don't have my git trees. svn is sufficient.

> Old version is quickly searchable by google.

Using old version is fine.
What you are seeing is a bug which exists in kohsuke's version.

> Look here it's second place in search results:
> https://imgur.com/a/IKHY8
> And new version is impossible to find in searching engine, it's so sad.
> 

In my search result, my version is printed first.
URL of my version is explicitly shown in the LCJ2014-en_0.pdf file.
I can't afford investigating modified/variant versions which are called "udplogger".
I don't have control for preventing modified/variant versions from appearing. ;-)

Anyway, please report when you succeeded to reproduce slowdown problem.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2018-01-07  3:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  3:50 mikhail
2017-12-08  4:05 ` Darrick J. Wong
2017-12-08 10:18   ` Tetsuo Handa
2017-12-09 13:17     ` mikhail
2017-12-09 14:14       ` Tetsuo Handa
2017-12-10 21:49         ` mikhail
2017-12-11  0:14           ` Tetsuo Handa
2017-12-11  3:34             ` mikhail
2017-12-11  3:48               ` Tetsuo Handa
2018-01-06 14:17                 ` mikhail
2018-01-06 14:52                   ` Tetsuo Handa
2018-01-06 15:28                     ` mikhail
2018-01-06 15:48                       ` Tetsuo Handa
2018-01-06 17:24                         ` mikhail
2018-01-07  3:42                           ` Tetsuo Handa [this message]
2017-12-09 12:31   ` mikhail
  -- strict thread matches above, loose matches on Subject: below --
2017-12-08  3:48 mikhail

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=201801071242.CCD05710.HFFVQJMtOOFOSL@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=darrick.wong@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    /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