From: Christoph Hellwig <hch@caldera.de>
To: Adam Keys <akeys@post.cis.smu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] kthread abstraction
Date: Fri, 1 Feb 2002 17:40:01 +0100 [thread overview]
Message-ID: <20020201174001.A4448@caldera.de> (raw)
In-Reply-To: <20020201163818.A32551@caldera.de> <20020201163337.DHBU26243.rwcrmhc51.attbi.com@there>
In-Reply-To: <20020201163337.DHBU26243.rwcrmhc51.attbi.com@there>; from akeys@post.cis.smu.edu on Fri, Feb 01, 2002 at 10:32:59AM -0600
On Fri, Feb 01, 2002 at 10:32:59AM -0600, Adam Keys wrote:
> On February 01, 2002 09:38, Christoph Hellwig wrote:
> > Currently the startup of custom kernel threads contains lots
> > of duplicated code (and bugs!).
>
> Very interesting and approachable patch. Am I correct this replaces the API
> for starting threads like bdflush and kswapd? Is this just an API
> cleanliness thing or is there a performance motivation?
It layers ontop of the old kernel_thread() API.
Currently all user had to duplicate the surrounding code - I've just
created a bunch of helper routines.
> > void kthread_stop(struct kthread *kth)
>
> Do you think you could get by just passing struct task_struct here? I
> realize that would make it less pleasant for calling functions. However, it
> would also prevent you from changing something else in the kthread in a later
> version and catching a caller by surprise.
No - I need the other struct kthread fields - that's why the structure
exists in the first time..
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2002-02-01 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 15:38 [PATCH][RFC] kthread abstraction Christoph Hellwig
2002-02-01 16:32 ` Adam Keys
2002-02-01 16:40 ` Christoph Hellwig [this message]
2002-02-01 17:21 ` Dave Hansen
2002-02-01 17:23 ` Christoph Hellwig
2002-02-01 17:49 ` Dave Hansen
2002-02-01 17:50 ` Jeff Garzik
[not found] <20020201163818.A32551@caldera.de.suse.lists.linux.kernel>
2002-02-01 16:50 ` Andi Kleen
2002-02-01 17:07 ` Christoph Hellwig
2002-02-01 17:17 ` Christoph Hellwig
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=20020201174001.A4448@caldera.de \
--to=hch@caldera.de \
--cc=akeys@post.cis.smu.edu \
--cc=linux-kernel@vger.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 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.