linux-kernel - Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Jun 2008 23:47:12 -0500
From:	Paul Jackson <pj@....com>
To:	Max Krasnyansky <maxk@...lcomm.com>
Cc:	ioe-lkml@...eria.de, sivanich@....com, a.p.zijlstra@...llo.nl,
	linux-kernel@...r.kernel.org, kernel@...ivas.org, dfults@....com,
	devik@....cz, dino@...ibm.com, emmanuel.pacaud@...v-poitiers.fr,
	deweerdt@...e.fr, mingo@...e.hu, colpatch@...ibm.com,
	nickpiggin@...oo.com.au, rostedt@...dmis.org, oleg@...sign.ru,
	paulmck@...ibm.com, menage@...gle.com, rddunlap@...l.org,
	suresh.b.siddha@...el.com, tglx@...utronix.de
Subject: Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may
 have realtime uses)

Max wrote:
> Ingo's case is a bad example.

Could be ... I wasn't paying close attention to the details.

If so, a good product marketing manager would first upsell the customer
to the better product, and then let falling sales guide the removal
of the old product.

That is, if you can guide most of the users of "isolcpus=" to a better
solution, in -their- view, so that they voluntary choose to migrate
to the other solution, then you get to deprecate and then remove the
old mechanism.

To the extent that you can show that the old mechanism is costing us
(maintenance, reliability, performance, impeding progress, ...) then
you get to accelerate the deprecation period, even to the point of
an immediate removal of the old feature, if it's of sufficiently little
use and great pain.

We do have one problem with letting "falling sales" guide feature
removal.  Unlike Walmart, where they know what has sold where before
the customer has even left the store, we can't easily track usage of
kernel features.  Occassionally, we can stir the pot and get some
feedback, as I've done on this thread, if we have a narrow target
audience that we have good reason is especially interested.  But that
only works occassionally.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/