From: Hugh Dickins <hugh@veritas.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: please revert kthread from loop.c
Date: Wed, 28 Jun 2006 19:41:10 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606281933300.24170@blonde.wat.veritas.com> (raw)
In-Reply-To: <20060627054612.GA15657@sergelap.austin.ibm.com>
On Tue, 27 Jun 2006, Serge E. Hallyn wrote:
>
> Very sorry.
No problem, just something I happened to notice, that's all.
> Subject: [PATCH] kthread: convert loop.c to use kthread
>
> Convert loop.c to use kthread in place of the deprecated
> kernel_thread.
>
> Update: Keep the lo_done completion to indicate when the
> loop_thread is ready. Otherwise a user gets the
> go-ahead early and may start an ioctl before
> loop_thread is in fact ready.
>
> Also fix some other bugs including misnaming the thread,
> found by Andrew Morton, and not setting lo->thread as
> pointed out by Hugh Dickins.
>
> This version has passed parallel runs of the following
> script (on different devices of course), i.e.
But not good for me. Gets further e.g. 170 iterations,
but then hangs while kthread_stop waits for completion.
I haven't investigated further. Is there really any reason
to be messing with what has worked well for so long here?
Hugh
next prev parent reply other threads:[~2006-06-28 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 18:39 Hugh Dickins
2006-06-27 5:46 ` Serge E. Hallyn
2006-06-28 18:41 ` Hugh Dickins [this message]
2006-06-28 19:08 ` Serge E. Hallyn
2006-07-11 19:49 ` Serge E. Hallyn
2006-07-12 0:17 ` Andrew Morton
2006-07-12 3:26 ` Serge E. Hallyn
2006-07-12 3:46 ` Andrew Morton
2006-07-12 14:31 ` Serge E. Hallyn
2006-07-12 23:02 ` Serge E. Hallyn
2006-07-13 9:38 ` Andrew Morton
2006-07-13 13:36 ` Serge E. Hallyn
2006-07-13 14:57 ` Andrew Morton
2006-07-20 17:00 ` Serge E. Hallyn
2006-07-12 15:13 ` Hugh Dickins
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=Pine.LNX.4.64.0606281933300.24170@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®