1. 01 Feb, 2011 10 commits
    • Tejun Heo's avatar
      net/9p: use system_wq instead of p9_mux_wq · 61edeeed
      Tejun Heo authored
      With cmwq, there's no reason to use a dedicated workqueue in trans_fd.
      Drop p9_mux_wq and use system_wq instead.  The used work items are
      already sync canceled in p9_conn_destroy() and doesn't require further
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Eric Van Hensbergen <ericvh@gmail.com>
      Cc: Ron Minnich <rminnich@sandia.gov>
      Cc: Latchesar Ionkov <lucho@ionkov.net>
      Cc: v9fs-developer@lists.sourceforge.net
    • Tejun Heo's avatar
      xfs: convert to alloc_workqueue() · 83e75904
      Tejun Heo authored
      Convert from create[_singlethread]_workqueue() to alloc_workqueue().
      * xfsdatad_workqueue and xfsconvertd_workqueue are identity converted.
        Using higher concurrency limit might be useful but given the
        complexity of workqueue usage in xfs, proceeding cautiously seems
      * xfs_mru_reap_wq is converted to non-ordered workqueue with max
        concurrency of 1 as the work items don't require any specific
        ordering and already have proper synchronization.  It seems it was
        singlethreaded to save worker threads, which is no longer a concern.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Alex Elder <aelder@sgi.com>
      Cc: xfs-masters@oss.sgi.com
      Cc: Christoph Hellwig <hch@infradead.org>
    • Tejun Heo's avatar
      reiserfs: make commit_wq use the default concurrency level · 28aadf51
      Tejun Heo authored
      The maximum number of concurrent work items queued on commit_wq is
      bound by the number of active journals.  Convert to alloc_workqueue()
      and use the default concurrency level so that they can be processed in
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: reiserfs-devel@vger.kernel.org
    • Tejun Heo's avatar
      ocfs2: use system_wq instead of ocfs2_quota_wq · 316873c9
      Tejun Heo authored
      ocfs2_quota_wq is not depended upon during memory reclaim and, with
      cmwq, there's no reason to use a dedicated workqueue.  Drop
      ocfs2_quota_wq and use system_wq instead.  dqi_sync_work is already
      sync canceled on quota disable and no further synchronization is
      This change makes ocfs2_quota_setup/shutdown() noops.  Both functions
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Mark Fasheh <mfasheh@suse.com>
      Cc: Joel Becker <joel.becker@oracle.com>
    • Tejun Heo's avatar
      ext4: convert to alloc_workqueue() · fd89d5f2
      Tejun Heo authored
      Convert create_workqueue() to alloc_workqueue().  This is an identity
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: "Theodore Ts'o" <tytso@mit.edu>
      Cc: Andreas Dilger <adilger.kernel@dilger.ca>
      Cc: linux-ext4@vger.kernel.org
    • Tejun Heo's avatar
      scsi/scsi_tgt_lib: scsi_tgtd isn't used in memory reclaim path · 40f38ffb
      Tejun Heo authored
      Workqueue scsi_tgtd isn't used during memory reclaim.  Convert to
      alloc_workqueue() without WQ_MEM_RECLAIM.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: FUJITA Tomonori <tomof@acm.org>
      Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
      Cc: linux-scsi@vger.kernel.org
    • Tejun Heo's avatar
      scsi/be2iscsi,qla2xxx: convert to alloc_workqueue() · 278274d5
      Tejun Heo authored
      Switch to new workqueue interface alloc_workqueue().  These are
      identity conversions.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Acked-by: default avatarMadhuranath Iyengar <Madhu.Iyengar@qlogic.com>
      Cc: Jayamohan Kallickal <jayamohank@serverengines.com>
      Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>
      Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
      Cc: linux-scsi@vger.kernel.org
    • Tejun Heo's avatar
      misc/iwmc3200top: use system_wq instead of dedicated workqueues · 51f50f81
      Tejun Heo authored
      With cmwq, there's no reason to use separate workqueues in
      iwmc3200top.  Drop them and use system_wq instead.  The used work
      items are sync flushed before driver detach.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Tomas Winkler <tomas.winkler@intel.com>
    • Tejun Heo's avatar
      i2o: use alloc_workqueue() instead of create_workqueue() · 52286713
      Tejun Heo authored
      This is an identity conversion.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Markus Lidel <Markus.Lidel@shadowconnect.com>
    • Tejun Heo's avatar
      acpi: kacpi*_wq don't need WQ_MEM_RECLAIM · 44d2588e
      Tejun Heo authored
      ACPI workqueues aren't used during memory reclaming.  Use
      alloc_workqueue() to create workqueues w/o rescuers.
      If the purpose of the separation between kacpid_wq and kacpi_notify_wq
      was to give notifications better response time, kacpi_notify_wq can be
      dropped and kacpi_wq can be created with higher @max_active.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Cc: Len Brown <lenb@kernel.org>
      Cc: linux-acpi@vger.kernel.org
  2. 26 Jan, 2011 5 commits
  3. 25 Jan, 2011 1 commit
  4. 24 Jan, 2011 22 commits
  5. 23 Jan, 2011 2 commits
    • Rob Landley's avatar
      Make CIFS mount work in a container. · f1d0c998
      Rob Landley authored
      Teach cifs about network namespaces, so mounting uses adresses/routing
      visible from the container rather than from init context.
      A container is a chroot on steroids that changes more than just the root
      filesystem the new processes see.  One thing containers can isolate is
      "network namespaces", meaning each container can have its own set of
      ethernet interfaces, each with its own own IP address and routing to the
      outside world.  And if you open a socket in _userspace_ from processes
      within such a container, this works fine.
      But sockets opened from within the kernel still use a single global
      networking context in a lot of places, meaning the new socket's address
      and routing are correct for PID 1 on the host, but are _not_ what
      userspace processes in the container get to use.
      So when you mount a network filesystem from within in a container, the
      mount code in the CIFS driver uses the host's networking context and not
      the container's networking context, so it gets the wrong address, uses
      the wrong routing, and may even try to go out an interface that the
      container can't even access...  Bad stuff.
      This patch copies the mount process's network context into the CIFS
      structure that stores the rest of the server information for that mount
      point, and changes the socket open code to use the saved network context
      instead of the global network context.  I.E. "when you attempt to use
      these addresses, do so relative to THIS set of network interfaces and
      routing rules, not the old global context from back before we supported
      The big long HOWTO sets up a test environment on the assumption you've
      never used ocntainers before.  It basically says:
      1) configure and build a new kernel that has container support
      2) build a new root filesystem that includes the userspace container
      control package (LXC)
      3) package/run them under KVM (so you don't have to mess up your host
      system in order to play with containers).
      4) set up some containers under the KVM system
      5) set up contradictory routing in the KVM system and the container so
      that the host and the container see different things for the same address
      6) try to mount a CIFS share from both contexts so you can both force it
      to work and force it to fail.
      For a long drawn out test reproduction sequence, see:
        http://landley.livejournal.com/47476.htmlSigned-off-by: default avatarRob Landley <rlandley@parallels.com>
      Reviewed-by: default avatarJeff Layton <jlayton@redhat.com>
      Signed-off-by: default avatarSteve French <sfrench@us.ibm.com>
    • Rusty Russell's avatar
      Remove MAYBE_BUILD_BUG_ON · 1765e3a4
      Rusty Russell authored
      Now BUILD_BUG_ON() can handle optimizable constants, we don't need
      MAYBE_BUILD_BUG_ON any more.
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>