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: <CACVXFVNMfe1bGRmeQf-xKxA=YnD8e=dXwBQmoJzx_HNiPFJYHQ@mail.gmail.com> Date: Thu, 11 Sep 2014 07:53:09 +0800 From: Ming Lei <ming.lei@...onical.com> To: Christoph Hellwig <hch@...radead.org> Cc: Jens Axboe <axboe@...nel.dk>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux SCSI List <linux-scsi@...r.kernel.org>, Christoph Hellwig <hch@....de> Subject: Re: [PATCH 8/8] blk-mq: support per-distpatch_queue flush machinery On Thu, Sep 11, 2014 at 3:02 AM, Christoph Hellwig <hch@...radead.org> wrote: > On Wed, Sep 10, 2014 at 09:40:11AM +0800, Ming Lei wrote: >> I am wondering we can do that because lifetime is totally different >> between flush requests and tag_set requests which are initialized >> before request queue is created. > > We shouldn't do it in the tag sets, but where we allocate and free > each hctx: blk_mq_init_queue and blk_mq_free_hw_queues. That should work, but both flush queue's allocation and .init_request() have to move to the function because hctx->numa_node is basically ready in blk_mq_init_queue(). Then blk_init_flush() only need to allocate the data for legacy case. Thanks, -- 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