linux-kernel - Re: [PATCH 1/3] block: loop: use kmap(page) instead of page

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACVXFVMaoD0=Lc6fkaUXGLkzUyYK0x543sapegjazVwafo9FFw@mail.gmail.com>
Date:	Tue, 24 Mar 2015 19:24:02 +0800
From:	Ming Lei <ming.lei@...onical.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Jens Axboe <axboe@...com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Maxim Patlasov <mpatlasov@...allels.com>
Subject: Re: [PATCH 1/3] block: loop: use kmap(page) instead of page_address(page)

On Tue, Mar 24, 2015 at 7:09 PM, Christoph Hellwig <hch@....de> wrote:
> On Tue, Mar 24, 2015 at 06:49:00PM +0800, Ming Lei wrote:
>> On 32bit system, this still may cause pressure on page allocation, since
>> requests are handled concurrently now after using workqueue.
>
> kmap slots are from a much smaller resource pool than non-highmem
> allocations, so if a page needs to stay kmaped from allocation time until
> freeing it it should just be allocated as a kernel mapped page.

Yeah, that makes sense to use non-highmem.

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/