mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Rusty Russell <rusty@rustcorp.com.au>,
	arjan@linux.intel.com
Subject: [GIT PULL] async changes for 3.9-rc1
Date: Tue, 19 Feb 2013 10:07:22 -0800	[thread overview]
Message-ID: <20130219180722.GO17414@htj.dyndns.org> (raw)

Hello, Linus.

These are followups for the earlier deadlock issue involving async
ending up waiting for itself through block requesting module[1].  The
following changes are made by these commits.

* Instead of requesting default elevator on each request_queue init,
  block now requests it once early during boot.

* Kmod triggers warning if invoked from an async worker.

* Async synchronization implementation has been reimplemented.  It's a
  lot simpler now.

This branch depends on wq/for-3.9 for current_is_async() and this pull
request assumes that wq/for-3.9 is already pulled in.  It also
contains a pull from 3.8-rc4 to base async synchronization
reimplementation on top of async fixes there.

The changes are available in the following git branch

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-3.9-async

for you to fetch changes up to a0327ff0eda915be623658babacef706099c11a8:

  async: initialise list heads to fix crash (2013-01-25 09:14:48 -0800)

----------------------------------------------------------------
James Hogan (1):
      async: initialise list heads to fix crash

Tejun Heo (8):
      init, block: try to load default elevator module early during boot
      block: don't request module during elevator init
      async, kmod: warn on synchronous request_module() from async workers
      Merge branch 'master' into for-3.9-async
      async: bring sanity to the use of words domain and running
      async: use ULLONG_MAX for infinity cookie value
      async: keep pending tasks on async_domain and remove async_pending
      async: replace list of active domains with global list of pending items

 block/elevator.c            |  35 +++++++--
 include/linux/async.h       |  10 +--
 include/linux/elevator.h    |   5 ++
 include/linux/init.h        |   1 +
 init/do_mounts_initrd.c     |   3 +
 init/initramfs.c            |   8 +-
 init/main.c                 |  16 ++++
 kernel/async.c              | 167 ++++++++++++++++++-----------------------
 kernel/kmod.c               |   9 +++
 kernel/sched/core.c         |   2 +-
 kernel/workqueue.c          | 178 +++++++++++++++++---------------------------
 kernel/workqueue_internal.h |  66 ++++++++++++++++
 kernel/workqueue_sched.h    |   9 ---
 13 files changed, 280 insertions(+), 229 deletions(-)
 create mode 100644 kernel/workqueue_internal.h
 delete mode 100644 kernel/workqueue_sched.h

Thanks.

--
tejun

[1] http://thread.gmane.org/gmane.linux.kernel/1420814

                 reply	other threads:[~2013-02-19 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130219180722.GO17414@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=arjan@linux.intel.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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®