From: Tejun Heo <tj@kernel.org>
To: Lianwei Wang <lianwei.wang@gmail.com>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: PATCH: freezer: add fake signal clearing back when thaw task
Date: Mon, 4 Mar 2013 09:01:59 -0800 [thread overview]
Message-ID: <20130304170159.GA30413@htj.dyndns.org> (raw)
In-Reply-To: <CAJFUiJjy-7sS9xH76XMLs5SU6fUQ1Bk4Xn67jjHeZNQRjC54dg@mail.gmail.com>
Hello,
On Mon, Mar 04, 2013 at 11:24:06AM +0800, Lianwei Wang wrote:
> Freeze/Thaw is a hot path for the Linux based mobile OS, e.g. Android.
> If we don't remove the pending fake signal, then the user space apps
Hotness is relative. How often are we talking about? Do you have any
numbers backing up that this actually makes any difference? The
reason why I'm not convinced is that by the time the control reaches
fake_signal_clear() the system already has done most of the heavy
lifting and the code path which would be excluded by the extra
checking seems pretty short. If you can show otherwise, please do so.
> or the related kernel driver has to handle such error. And yes, the
> user can handle such case by checking the return value, but it mislead
> the user and confuse to them that why wait_event_freezable and friends
> return a error on resume path every time? Can we avoid such useless
> error return?
-ERESTARTSYS may happen without freezing and the syscall path has been
capable of handling it for a very long time. Again, do you have
anything which shows otherwise?
Thanks.
--
tejun
next prev parent reply other threads:[~2013-03-04 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 6:19 Lianwei Wang
2013-02-25 23:53 ` Tejun Heo
2013-02-26 14:14 ` Oleg Nesterov
2013-02-26 14:54 ` Oleg Nesterov
2013-02-26 14:28 ` Oleg Nesterov
2013-03-04 3:24 ` Lianwei Wang
2013-03-04 17:01 ` Tejun Heo [this message]
2013-03-04 17:32 ` Oleg Nesterov
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=20130304170159.GA30413@htj.dyndns.org \
--to=tj@kernel.org \
--cc=lianwei.wang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®