From: Denys Vlasenko <vda.linux@googlemail.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: Does process need to have a kernel-side stack all the time?
Date: Mon, 14 Apr 2008 16:54:22 +0200 [thread overview]
Message-ID: <200804141654.22513.vda.linux@googlemail.com> (raw)
In-Reply-To: <1208182649.7688.7.camel@iris.sw.ru>
On Monday 14 April 2008 16:17, Denis V. Lunev wrote:
> On Mon, 2008-04-14 at 15:47 +0200, Denys Vlasenko wrote:
> > Currently, when process sleeps, we save some
> > state in stack, and such a change may require
> > some substantial surgery.
> >
> > Can you tell me whether this is possible at all,
> > and how difficult you estimate it to be?
>
> I do not think that this can help. Usually, the process (thread) invokes
> some syscall like sleep and goes to the waiting state _from the kernel_,
> i.e. the kernel stack is used at that moment and will be required during
> wake up.
See my quote above. That's exactly what I said. This is how it currently
works.
But do you really need 4k to remember that "this thread went to sleep by
executing sleep(60)"? Theoretically, you may get away with much smaller
save area to remember that, and be able to wake up and return to userspace.
--
vda
next prev parent reply other threads:[~2008-04-14 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 13:47 Does process need to have a kernel-side stack all the time? Denys Vlasenko
2008-04-14 14:17 ` Denis V. Lunev
2008-04-14 14:54 ` Denys Vlasenko [this message]
2008-04-14 15:21 ` Ingo Molnar
2008-04-14 17:44 ` Andi Kleen
2008-04-14 18:42 ` Denys Vlasenko
2008-04-16 12:47 ` Ingo Molnar
2008-04-16 13:02 ` Andi Kleen
2008-04-16 13:54 ` Arjan van de Ven
2008-04-16 13:59 ` Andi Kleen
2008-04-16 14:31 ` Arjan van de Ven
2008-04-16 14:20 ` Denys Vlasenko
2008-04-16 14:34 ` Arjan van de Ven
2008-04-14 23:21 ` Chris Snook
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=200804141654.22513.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=den@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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