From: Chintan Pandya <cpandya@codeaurora.org>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ksm: provide support to use deferrable timers for scanner thread
Date: Wed, 20 Aug 2014 17:24:51 +0530 [thread overview]
Message-ID: <53F48C8B.4020707@codeaurora.org> (raw)
In-Reply-To: <53EA3FF5.1050709@codeaurora.org>
Hi Hugh,
>>> + unsigned long enable;
>>> + int err;
>>> +
>>> + err = kstrtoul(buf, 10,&enable);
>>> + if (err< 0)
>>> + return err;
>>> + if (enable>= 1)
>>> + return -EINVAL;
>>
>> I haven't studied the patch itself, I'm still worrying about the concept.
>> But this caught my eye just before hitting Send: I don't think we need
>> a tunable which only accepts the value 0 ;)
>
> Okay. I can correct this to accept any non-zero value. Is that okay ?
I missed that to reply earlier. This was suggested by Andrew. And I
think that is okay as displaying any non-zero value to user via this
knob may not be completely right.
>
>>
>>> + use_deferrable_timer = enable;
>
--
Chintan Pandya
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Chintan Pandya <cpandya@codeaurora.org>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 2/2] ksm: provide support to use deferrable timers for scanner thread
Date: Wed, 20 Aug 2014 17:24:51 +0530 [thread overview]
Message-ID: <53F48C8B.4020707@codeaurora.org> (raw)
In-Reply-To: <53EA3FF5.1050709@codeaurora.org>
Hi Hugh,
>>> + unsigned long enable;
>>> + int err;
>>> +
>>> + err = kstrtoul(buf, 10,&enable);
>>> + if (err< 0)
>>> + return err;
>>> + if (enable>= 1)
>>> + return -EINVAL;
>>
>> I haven't studied the patch itself, I'm still worrying about the concept.
>> But this caught my eye just before hitting Send: I don't think we need
>> a tunable which only accepts the value 0 ;)
>
> Okay. I can correct this to accept any non-zero value. Is that okay ?
I missed that to reply earlier. This was suggested by Andrew. And I
think that is okay as displaying any non-zero value to user via this
knob may not be completely right.
>
>>
>>> + use_deferrable_timer = enable;
>
--
Chintan Pandya
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-08-20 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 7:59 [PATCH v3 1/2] timer: provide an api for deferrable timeout Chintan Pandya
2014-07-31 7:59 ` Chintan Pandya
2014-07-31 7:59 ` [PATCH v3 2/2] ksm: provide support to use deferrable timers for scanner thread Chintan Pandya
2014-07-31 7:59 ` Chintan Pandya
2014-08-11 12:18 ` Hugh Dickins
2014-08-11 12:18 ` Hugh Dickins
2014-08-12 16:25 ` Chintan Pandya
2014-08-12 16:25 ` Chintan Pandya
2014-08-20 11:54 ` Chintan Pandya [this message]
2014-08-20 11:54 ` Chintan Pandya
2014-08-04 9:26 ` [PATCH v3 1/2] timer: provide an api for deferrable timeout Chintan Pandya
2014-08-04 9:26 ` Chintan Pandya
2014-08-04 10:44 ` Peter Zijlstra
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=53F48C8B.4020707@codeaurora.org \
--to=cpandya@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.