linux-kernel - Re: pagevecs of more than PAGEVEC

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]

Date:	Fri, 23 May 2008 13:29:38 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Steve French <smfrench@...il.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: pagevecs of more than PAGEVEC_SIZE pages

Hi.

On Thu, May 22, 2008 at 10:54:59PM -0700, Andrew Morton (akpm@...ux-foundation.org) wrote:
> > Now that various servers support processing larger than 64K file
> > writes, it would be helpful to have pagevecs that are larger than 14
> > pages (PAGEVEC_SIZE).so an array of more pages could be passed to
> > kernel_sendmsg (thus allowing writes larger than 56K, depending on
> > wsize - the server limit is currently 8MB)
> 
> You can pass multiple pagevecs into kernel_sendmsg?

kernel_sendmsg() requires iovecs, so each page will have to be mapped,
which can end up having too many slots in kmap table. I can reproduce
deadlock we talked about in POHMELFS thread with 100 highmem pages per
transaction on 32bit x86, so increasing pagevec noticebly can deadlock
CIFS too.

It could be great if CIFS moved to kernel_sendpage() instead, Steve?

-- 
	Evgeniy Polyakov
--
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/