lkml.org 
[lkml]   [2012]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] kconfig: untangle EXPERT and EMBEDDED
On Wed, 18 Jan 2012, Andrew Jones wrote:

> > > Now changing it, i.e. making it conform more closely to its name and only
> > > affect embedded related options, you can't do. If you were to do so, then
> > > you would lose backward compatibility. How do you know there aren't users
> > > that started using EMBEDDED for the non-embedded side effects?
> >
> > That's why they're now using EXPERT.
>
> How do you know they've all switched?
>

Because existing CONFIG_EMBEDDED configs now automatically enable it since
my patch was merged a year ago. Users who haven't upgraded since then and
run make oldconfig will do so in the future and we're not risking breaking
backwards compatibility at least until a sufficient amount of time has
passed.

> > No, because they've already enabled EXPERT. You can't have EMBEDDED=y and
> > EXPERT=n. That's what this little thing called "select" does. After a
> > sufficient amount of time passes and all options that are important only
> > for embedded users have been either extended for EMBEDDED or replaced only
> > be EMBEDDED, you can get rid of the "select" without losing backwards
> > compatibility.
>
> How do you define a sufficient amount of time? How do you know everyone
> else agrees with that definition? OIOW, where is it documented? If it is
> documented, then how do you know everyone will read it and comply to it?
>

An example: when I rewrote the kernel oom killer and deprecated
/proc/pid/oom_adj, we did this:

- mapped writes to oom_adj to the new tunable, oom_score_adj,

- emitted a warning when userspace wrote to oom_adj a single time,

- a year later, emitted a warning every time userspace writes to
oom_adj, and

- in September of 2012, the tunable will be removed entirely.

This gives userspace two years to covert before the tunable is dropped
entirely. We can't keep it around forever, but we're careful not to
suddenly drop existing users without some due diligence. It's added to
Documentation/feature-removal-schedule.txt like all feature removals are.
We can do no better without a huge maintenance burden.

We could add that CONFIG_EMBEDDED will stop automatically enabling
CONFIG_EXPERT in January 2014 to
Documentation/feature-removal-schedule.txt as well. That certainly seems
like a good idea.

However, we've now diverged entirely from your patch in this thread.


\
 
 \ /
  Last update: 2012-01-18 10:23    [W:0.086 / U:0.372 seconds]
©2003-2014 Jasper Spaans. Advertise on this site