Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 01 2月, 2011 12 次提交
    • T
      rds/ib: use system_wq instead of rds_ib_fmr_wq · c534a107
      由 Tejun Heo 提交于 
      With cmwq, there's no reason to use dedicated rds_ib_fmr_wq - it's not
in the memory reclaim path and the maximum number of concurrent work
items is bound by the number of devices.  Drop it and use system_wq
instead.  This rds_ib_fmr_init/exit() noops.  Both removed.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: Andy Grover <andy.grover@oracle.com>
      c534a107
    • T
      net/9p: replace p9_poll_task with a work · aa70c585
      由 Tejun Heo 提交于 
      Now that cmwq can handle high concurrency, it's more efficient to use
work than a dedicated kthread.  Convert p9_poll_proc() to a work
function for p9_poll_work and make p9_pollwake() schedule it on each
poll event.  The work is sync flushed on module exit.
Signed-off-by: NTejun 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
      aa70c585
    • T
      net/9p: use system_wq instead of p9_mux_wq · 61edeeed
      由 Tejun Heo 提交于 
      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
synchronization.
Signed-off-by: NTejun 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
      61edeeed
    • T
      xfs: convert to alloc_workqueue() · 83e75904
      由 Tejun Heo 提交于 
      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
  better.

* 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: NTejun Heo <tj@kernel.org>
Cc: Alex Elder <aelder@sgi.com>
Cc: xfs-masters@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>
      83e75904
    • T
      reiserfs: make commit_wq use the default concurrency level · 28aadf51
      由 Tejun Heo 提交于 
      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
parallel.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: reiserfs-devel@vger.kernel.org
      28aadf51
    • T
      ocfs2: use system_wq instead of ocfs2_quota_wq · 316873c9
      由 Tejun Heo 提交于 
      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
necessary.

This change makes ocfs2_quota_setup/shutdown() noops.  Both functions
removed.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: Mark Fasheh <mfasheh@suse.com>
Cc: Joel Becker <joel.becker@oracle.com>
      316873c9
    • T
      ext4: convert to alloc_workqueue() · fd89d5f2
      由 Tejun Heo 提交于 
      Convert create_workqueue() to alloc_workqueue().  This is an identity
conversion.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: "Theodore Ts'o" <tytso@mit.edu>
Cc: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org
      fd89d5f2
    • T
      scsi/scsi_tgt_lib: scsi_tgtd isn't used in memory reclaim path · 40f38ffb
      由 Tejun Heo 提交于 
      Workqueue scsi_tgtd isn't used during memory reclaim.  Convert to
alloc_workqueue() without WQ_MEM_RECLAIM.
Signed-off-by: NTejun 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
      40f38ffb
    • T
      scsi/be2iscsi,qla2xxx: convert to alloc_workqueue() · 278274d5
      由 Tejun Heo 提交于 
      Switch to new workqueue interface alloc_workqueue().  These are
identity conversions.
Signed-off-by: NTejun Heo <tj@kernel.org>
Acked-by: NMadhuranath 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
      278274d5
    • T
      misc/iwmc3200top: use system_wq instead of dedicated workqueues · 51f50f81
      由 Tejun Heo 提交于 
      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: NTejun Heo <tj@kernel.org>
Cc: Tomas Winkler <tomas.winkler@intel.com>
      51f50f81
    • T
      i2o: use alloc_workqueue() instead of create_workqueue() · 52286713
      由 Tejun Heo 提交于 
      This is an identity conversion.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: Markus Lidel <Markus.Lidel@shadowconnect.com>
      52286713
    • T
      acpi: kacpi*_wq don't need WQ_MEM_RECLAIM · 44d2588e
      由 Tejun Heo 提交于 
      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: NTejun Heo <tj@kernel.org>
Cc: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
      44d2588e
  3. 27 1月, 2011 1 次提交
    • T
      fs/aio: aio_wq isn't used in memory reclaim path · d37adaa1
      由 Tejun Heo 提交于 
      aio_wq isn't used during memory reclaim.  Convert to alloc_workqueue()
without WQ_MEM_RECLAIM.  It's possible to use system_wq but given that
the number of work items is determined from userland and the work item
may block, enforcing strict concurrency limit would be a good idea.

Also, move fput_work to system_wq so that aio_wq is used soley to
throttle the max concurrency of aio work items and fput_work doesn't
interact with other work items.
Signed-off-by: NTejun Heo <tj@kernel.org>
Acked-by: NJeff Moyer <jmoyer@redhat.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-aio@kvack.org
      d37adaa1
  5. 26 1月, 2011 4 次提交
  7. 25 1月, 2011 19 次提交
  9. 24 1月, 2011 4 次提交