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
| ||
|
Message-Id: <20071206162915.a3917d1c.akpm@linux-foundation.org> Date: Thu, 6 Dec 2007 16:29:15 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Daniel Phillips <phillips@...nq.net> Cc: davidsen@....com, linux-kernel@...r.kernel.org, peterz@...radead.org Subject: Re: [RFC] [PATCH] A clean approach to writeout throttling On Thu, 6 Dec 2007 16:04:41 -0800 Daniel Phillips <phillips@...nq.net> wrote: > The runner up key idea is that we will gain a notion of "block device > stack" (or block stack for short, so that we may implement block > stackers) which for the time being will simply be Device Mapper's > notion of device stack, however many warts that may have. It's there > now and we use it for ddsnap. Perhaps all we need to track is the outermost point? submit_bio(...) { bool remove_the_rq = false; ... if (current->the_rq == NULL) { current->the_rq = rq; remove_the_rq = true; } ... if (remove_the_rq) current->the_rq = NULL; } ? -- 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