| 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
| ||
|
Date: Wed, 20 May 2009 13:39:18 +0200 From: Jens Axboe <jens.axboe@...cle.com> To: Jan Kara <jack@...e.cz> Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, chris.mason@...cle.com, david@...morbit.com, hch@...radead.org, akpm@...ux-foundation.org, yanmin_zhang@...ux.intel.com Subject: Re: [PATCH 04/11] writeback: separate the flushing state/task from the bdi On Wed, May 20 2009, Jan Kara wrote: > On Mon 18-05-09 14:19:45, Jens Axboe wrote: > > Add a struct bdi_writeback for tracking and handling dirty IO. This > > is in preparation for adding > 1 flusher task per bdi. > Some changes (IMO the most complicated ones ;) in this patch set seem to > be just reordering / cleanup of changes which happened in patch #2. Could > you maybe move it there. Commented below... Some of it, most of it is due to switching from one fixed thread to the potential of having lots more. The moving code around is mostly due to other callers now having to use functions that were below them, and I'd rather move them around instead of having prototypes at the top. It would be easy to unify the two patches, but I wanted to separate the switch from pdflush to 1 bdi thread from the transition from 1 bdi thread to several. -- 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/
Powered by blists - more mailing lists