From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH] net: don't use kvzalloc for DMA memory Date: Thu, 19 Apr 2018 07:00:53 +0300 Message-ID: <20180419065711-mutt-send-email-mst@kernel.org> References: <3e65977e-53cd-bf09-bc4b-0ce40e9091fe@gmail.com> <20180418204229-mutt-send-email-mst@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Mikulas Patocka , "David S. Miller" , Eric Dumazet , Joby Poriyath , Ben Hutchings , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Eric Dumazet Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, Apr 18, 2018 at 01:38:43PM -0700, Eric Dumazet wrote: > > > On 04/18/2018 10:55 AM, Michael S. Tsirkin wrote: > > > Imagine you want to pass some data to card. > > Natural thing is to just put it in a variable and start DMA. > > However DMA API disallows stack access nowdays, > > so it's natural to put this within struct device. > > > > See e.g. > > > > commit a725ee3e44e39dab1ec82cc745899a785d2a555e > > Author: Andy Lutomirski > > Date: Mon Jul 18 15:34:49 2016 -0700 > > > > virtio-net: Remove more stack DMA > > > > Andy just moved the problem to another one, since at that time we already > had vmalloc() fallback for at least 2 years. > > Note that my original patch had : > > p = kzalloc(alloc_size, GFP_KERNEL | __GFP_NOWARN | __GFP_REPEAT); > if (!p) > p = vzalloc(alloc_size); > > So really, normal (less than PAGE_SIZE) allocations would have almost-zero-chance to end up to vmalloc(one_page) Thanks Eric, I'll fix virtio. -- MST