From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [RFC] Don'd hold work_sem while calling worker functions
Date: Tue, 16 Sep 2014 15:26:36 +0200 [thread overview]
Message-ID: <1410873998-2955-1-git-send-email-richard@nod.at> (raw)
I fail to see why we need work_sem while wrk->func() is executed.
Artem, do you have an idea?
Having the wear_leveling_worker() called without work_sem held
would simplify the fastmap code too. I'm currently reworking some
of it's code and I'm in locking hell. 8-)
Thanks,
//richard
[PATCH 1/2] UBI: Call worker functions without work_sem held
[PATCH 2/2] UBI: Get rid of __schedule_ubi_work()
next reply other threads:[~2014-09-16 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 13:26 Richard Weinberger [this message]
2014-09-16 13:26 ` [PATCH 1/2] UBI: Call worker functions without work_sem held Richard Weinberger
2014-09-16 13:26 ` [PATCH 2/2] UBI: Get rid of __schedule_ubi_work() Richard Weinberger
2014-09-17 8:42 ` [RFC] Don'd hold work_sem while calling worker functions 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=1410873998-2955-1-git-send-email-richard@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).