From: "H. Peter Anvin" <hpa@zytor.com>
To: josh@joshtriplett.org
Cc: boris.ostrovsky@oracle.com, david.vrabel@citrix.com,
ksummit-discuss@lists.linuxfoundation.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code.
Date: Wed, 11 Jun 2014 08:56:44 -0700 [thread overview]
Message-ID: <53987C3C.3080808@zytor.com> (raw)
In-Reply-To: <20140611003606.GA11052@cloud>
On 06/10/2014 05:36 PM, josh@joshtriplett.org wrote:
>
> I agree. I think we've had some recent examples of how to do this
> better, with remap_file_pages: old userspace has to *work* on new
> kernels, but it doesn't necessarily need to run fast, or integrate with
> any new features. We should deprecate more kernel bits in
> favor of minimal compatibility layers, some of which we can associate
> with old userspace and drop for new userspace.
>
Uhm... that applies only to a fairly restricted aspect of deprecation.
Much more is tied to specific hardware.
-hpa
next prev parent reply other threads:[~2014-06-11 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 20:12 [Ksummit-discuss] Topic: Removal of code that is still in use by users but there is a better code Konrad Rzeszutek Wilk
2014-06-10 20:19 ` H. Peter Anvin
2014-06-11 0:36 ` josh
2014-06-11 15:56 ` H. Peter Anvin [this message]
2014-06-11 20:02 ` josh
2014-06-11 17:54 ` Guenter Roeck
2014-06-11 19:43 ` Bjorn Helgaas
2014-06-11 21:53 ` Stephen Rothwell
2014-06-11 22:01 ` Andy Lutomirski
2014-06-11 22:17 ` James Bottomley
2014-06-11 22:26 ` Roland Dreier
2014-06-11 22:36 ` James Bottomley
2014-06-12 11:41 ` Rafael J. Wysocki
2014-06-12 13:27 ` John W. Linville
2014-06-13 1:36 ` James Bottomley
2014-06-19 13:01 ` Linus Walleij
2014-06-11 23:22 ` Guenter Roeck
2014-06-12 2:48 ` Steven Rostedt
2014-06-12 7:16 ` Geert Uytterhoeven
2014-06-12 0:07 ` H. Peter Anvin
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=53987C3C.3080808@zytor.com \
--to=hpa@zytor.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=josh@joshtriplett.org \
--cc=konrad.wilk@oracle.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.