linux-kernel - [PATCH 0/12] Per-bdi writeback flusher threads v7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1243330430-9964-1-git-send-email-jens.axboe@oracle.com>
Date:	Tue, 26 May 2009 11:33:38 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Cc:	chris.mason@...cle.com, david@...morbit.com, hch@...radead.org,
	akpm@...ux-foundation.org, jack@...e.cz,
	yanmin_zhang@...ux.intel.com, richard@....demon.co.uk
Subject: [PATCH 0/12] Per-bdi writeback flusher threads v7

Hi,

Here's the 7th version of the writeback patches. Changes since
v5/v6:

- Move the sync_supers() to the global bdi_forker_task() thread, so we
  don't writeback the supers from all the bdi kupdated() tasks.
- Make bdi_start_writeback() and bdi_writeback_all() be sync when called
  with WB_SYNC_ALL only.
- Shuffle some more things around to make a cleaner series. The sync vs
  async nature of bdi_writeback_all() and bdi_start_writeback() isn't
  consistent through the series, but otherwise things should be sane.

I'd appreciate if Richard and Yanmin could re-run testing with this,
just to make sure that things are sane. For ease of patching, I've
put the full diff here:

  http://kernel.dk/writeback-v7.patch

and also stored this in a writeback-v7 branch that will not change,
you can pull that into Linus tree from here:

  git://git.kernel.dk/linux-2.6-block.git writeback-v7

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/