From: Artem Bityutskiy <dedekind@infradead.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Alexander Schmidt <alexs@linux.vnet.ibm.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [RFC] [PATCH] UBI: convert to kthread API
Date: Tue, 27 Feb 2007 20:11:29 +0200 [thread overview]
Message-ID: <1172599889.17031.9.camel@sauron> (raw)
In-Reply-To: <1172599497.3885.2.camel@zod.rchland.ibm.com>
On Tue, 2007-02-27 at 12:04 -0600, Josh Boyer wrote:
> On Tue, 2007-02-27 at 19:47 +0200, Artem Bityutskiy wrote:
> > Hello Alexander,
> >
> > On Tue, 2007-02-27 at 14:50 +0100, Alexander Schmidt wrote:
> > > UBI should use the kthread API, which makes completions and signal
> > > handling go away.
> >
> > how feasible and possible is to get rid of this UBI unit altogether?
>
> Depends I suppose. Is it going to make a large runtime functionality or
> performance impact if a background thread isn't running?
Sorry for vagueness, I do not mean to remove th background _process_, we
really need it. I meant to remove the UBI unit source-wise and use the
kthread calls directly. I am busy with other stuff right now and wanted
Alexander to check how much ugliness or niceness we would introduce with
that change.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2007-02-27 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 13:50 [RFC] [PATCH] UBI: convert to kthread API Alexander Schmidt
2007-02-27 17:47 ` Artem Bityutskiy
2007-02-27 18:04 ` Josh Boyer
2007-02-27 18:11 ` Artem Bityutskiy [this message]
2007-02-28 8:15 ` Alexander Schmidt
2007-02-28 10:04 ` Artem Bityutskiy
2007-02-28 14:48 ` Alexander Schmidt
2007-02-28 16:13 ` Artem Bityutskiy
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=1172599889.17031.9.camel@sauron \
--to=dedekind@infradead.org \
--cc=alexs@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.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