From: Michal Hocko <mhocko@kernel.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: Change global memory state symbols to GPL-only
Date: Mon, 17 Aug 2015 17:11:45 +0200 [thread overview]
Message-ID: <20150817151145.GF10894@dhcp22.suse.cz> (raw)
In-Reply-To: <1439823392.10801.16.camel@decadent.org.uk>
On Mon 17-08-15 16:56:32, Ben Hutchings wrote:
> On Mon, 2015-08-17 at 15:54 +0200, Michal Hocko wrote:
> > On Sun 16-08-15 01:42:27, Ben Hutchings wrote:
> > > Proprietary modules should not be able to touch vm_stat or participate
> > > in shrinking.
> >
> > How does the external and !GPL fs does slab reclaim? Those are essential
> > for the proper memory balancing.
>
> If they know how to do shrinking on Linux then they are probably
> derivative works of Linux.
I am not sure I understand. They are shrinking their internal cached
objects and that is hardly a derivative work. The shrinker API is only
meant to let them know _when_ this should happen and the interface is
a pretty much simple callback API.
I do not want to defend a proprietary code here but this sounds like an
obstruction for those modules which will lead into a worse code in the
end because they should somehow manage the cache and it is much better
when the core (MM) tells them when it makes sense rather than external
heuristics.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2015-08-17 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 23:42 Ben Hutchings
2015-08-17 13:54 ` Michal Hocko
2015-08-17 14:56 ` Ben Hutchings
2015-08-17 15:11 ` Michal Hocko [this message]
2015-08-17 16:51 ` Ben Hutchings
2015-09-01 1:24 Richard Yao
2015-09-01 2:51 ` Dave Chinner
2015-09-01 13:21 ` Ben Hutchings
2015-09-01 17:29 ` Richard Yao
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=20150817151145.GF10894@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®