public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Simon Horman <horms@verge.net.au>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Stable Kernel <stable@kernel.org>,
	"dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>
Subject: Re: [PATCH] xen: make sysfs files behave as their names suggest
Date: Wed, 28 Jan 2009 20:31:25 -0800	[thread overview]
Message-ID: <4981311D.9080205@goop.org> (raw)
In-Reply-To: <20090129023516.GB1319@verge.net.au>

Simon Horman wrote:
> On Wed, Jan 28, 2009 at 04:50:20PM -0800, Jeremy Fitzhardinge wrote:
>   
>> 1: make "target_kb" only accept and produce a memory size in kilobytes.
>> 2: add a second "target" file which produces output in bytes, and will accept
>>   memparse input (scaled bytes)
>>
>> This fixes the rather irritating problem that writing the same value
>> read back into target_kb would end up shrinking the domain by a factor
>> of 1024, with generally bad results.
>>     
>
> Are there any compatibility issues that we should care about
> related to this change?
>   

Well, in theory, but not in practice I think.

It changes the behaviour of target_kb from accepting bytes into 
kilobytes, and it no longer parses a k/m/g suffix.  The old behaviour 
was a definite bug, given the name of the file, so I consider this to be 
pure bugfix.  The kernel introducing this interface has only been out 
for a week or two, so I don't think there's much chance anyone has 
started relying on the buggy behaviour.

    J

  reply	other threads:[~2009-01-29  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  0:50 [PATCH] xen: make sysfs files behave as their names suggest Jeremy Fitzhardinge
2009-01-29  2:35 ` Simon Horman
2009-01-29  4:31   ` Jeremy Fitzhardinge [this message]
2009-01-29  6:44     ` Simon Horman
2009-01-29 12:20 ` Ingo Molnar

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=4981311D.9080205@goop.org \
    --to=jeremy@goop.org \
    --cc=dan.magenheimer@oracle.com \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable@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