From: Pavel Machek <pavel@ucw.cz>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, Mel Gorman <mgorman@suse.de>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Neil Brown <neilb@suse.de>,
Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] treewide: remove GFP_TEMPORARY allocation flag
Date: Thu, 31 Aug 2017 11:10:25 +0200 [thread overview]
Message-ID: <20170831091024.GB12920@amd> (raw)
In-Reply-To: <20170828123542.GJ17097@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]
Hi!
> > > > You can define more exact meaning, and then adjust the usage. But
> > > > there's no need to do treewide replacement...
> > >
> > > I have checked most of them and except for the initially added onces the
> > > large portion where added without a good reasons or even break an
> > > intuitive meaning by taking locks.
> >
> > I don't see it. kmalloc() itself takes locks. Of course everyone takes
> > locks. I don't think that's intuitive meaning.
>
> I was talking about users of the flag. I have seen some to take a lock
> right after they allocated GFP_TEMPORARY object.
Yes, I'd expect people to take locks after allocating temporary
objects. kmalloc itself takes locks. If the allocation is "usually"
freed within miliseconds, that should be enough.
> > > Seriously, if we need a short term semantic it should be clearly defined
> > > first.
> >
> > "milliseconds, not hours."
> >
> > > Is there any specific case why you think this patch is in a wrong
> > > direction? E.g. a measurable regression?
> >
> > Not playing that game. You should argue why it is improvement. And I
> > don't believe you did.
>
> Please read the whole changelog where I was quite verbose about how the
> current flag is abused and how its semantic is weak and encourages a
> wrong usage pattern. Moreover it is not even clear whether it helps
> anything. I haven't seen any actual counter argument from you other than
> "milliseconds not hours" without actually explaining how that would be
> useful for any decisions done in the core MM layer.
Well, I find that argumentation insufficient for global
search&replace.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-08-31 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 9:19 [RFC PATCH] treewide: remove GFP_TEMPORARY allocation flag Michal Hocko
2017-07-28 9:52 ` Mel Gorman
2017-07-28 10:27 ` Michal Hocko
2017-07-28 10:59 ` Mel Gorman
2017-07-28 13:15 ` Vlastimil Babka
2017-08-23 17:57 ` Pavel Machek
2017-08-25 6:35 ` Michal Hocko
2017-08-25 7:28 ` Pavel Machek
2017-08-25 8:04 ` Michal Hocko
2017-08-25 21:39 ` Pavel Machek
2017-08-26 4:11 ` NeilBrown
2017-08-28 12:36 ` Michal Hocko
2017-08-31 9:07 ` Pavel Machek
2017-08-31 9:29 ` Mel Gorman
2017-08-28 12:35 ` Michal Hocko
2017-08-31 9:10 ` Pavel Machek [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=20170831091024.GB12920@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=neilb@suse.de \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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).