From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH 05/15] Add io_uring IO interface Date: Thu, 17 Jan 2019 16:21:41 -0500 Message-ID: References: <20190116175003.17880-1-axboe@kernel.dk> <20190116175003.17880-6-axboe@kernel.dk> <718b4d1fbe9f97592d6d7b76d7a4537d@suse.de> <02568485-cd10-182d-98e3-619077cf9bdc@kernel.dk> <3180aa85-68a6-0eb2-082b-f177344cefa9@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Jens Axboe's message of "Thu, 17 Jan 2019 14:17:05 -0700") Sender: owner-linux-aio@kvack.org To: Jens Axboe Cc: Roman Penyaev , linux-fsdevel@vger.kernel.org, linux-aio@kvack.org, linux-block@vger.kernel.org, linux-arch@vger.kernel.org, hch@lst.de, avi@scylladb.com, linux-block-owner@vger.kernel.org List-Id: linux-arch.vger.kernel.org Jens Axboe writes: >> So all we need to do is modify gpg2 so that is requires more locked >> memory, and we're golden! ;-) > > Haha, that's some nice digging there! > > Yes, we could bump it, but with the default, we can get a 512 sized > ring per user, that's 13 pages (rounded up). Probably good enough to > get things off the ground? Agreed. I'll work on bloating gpg as a background task. =P Or I guess we could add instructions for modifying /etc/security/limits.conf to the man pages. Cheers, Jeff -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:55142 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726905AbfAQVVn (ORCPT ); Thu, 17 Jan 2019 16:21:43 -0500 From: Jeff Moyer Subject: Re: [PATCH 05/15] Add io_uring IO interface References: <20190116175003.17880-1-axboe@kernel.dk> <20190116175003.17880-6-axboe@kernel.dk> <718b4d1fbe9f97592d6d7b76d7a4537d@suse.de> <02568485-cd10-182d-98e3-619077cf9bdc@kernel.dk> <3180aa85-68a6-0eb2-082b-f177344cefa9@kernel.dk> Date: Thu, 17 Jan 2019 16:21:41 -0500 In-Reply-To: (Jens Axboe's message of "Thu, 17 Jan 2019 14:17:05 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-arch-owner@vger.kernel.org List-ID: To: Jens Axboe Cc: Roman Penyaev , linux-fsdevel@vger.kernel.org, linux-aio@kvack.org, linux-block@vger.kernel.org, linux-arch@vger.kernel.org, hch@lst.de, avi@scylladb.com, linux-block-owner@vger.kernel.org Message-ID: <20190117212141.kAG74hm9NW6QzgjVypRJdCSTdOy5uSawgZwvgToQh7w@z> Jens Axboe writes: >> So all we need to do is modify gpg2 so that is requires more locked >> memory, and we're golden! ;-) > > Haha, that's some nice digging there! > > Yes, we could bump it, but with the default, we can get a 512 sized > ring per user, that's 13 pages (rounded up). Probably good enough to > get things off the ground? Agreed. I'll work on bloating gpg as a background task. =P Or I guess we could add instructions for modifying /etc/security/limits.conf to the man pages. Cheers, Jeff