[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgSW3gB1=rf3atv=3Xvn0pNBtKUKJ2VF81ue-xagS7F4w@mail.gmail.com>
Date: Thu, 21 Apr 2022 09:30:59 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrei Vagin <avagin@...il.com>
Cc: kernel test robot <oliver.sang@...el.com>,
Dmitry Safonov <0x7f454c46@...il.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, lkp@...ts.01.org,
kernel test robot <lkp@...el.com>,
Mike Rapoport <rppt@...ux.ibm.com>
Subject: Re: [fs/pipe] 5a519c8fe4: WARNING:at_mm/page_alloc.c:#__alloc_pages
On Thu, Apr 21, 2022 at 8:35 AM Andrei Vagin <avagin@...il.com> wrote:
>
> The operation of injecting/curing parasite code from the
> process is expensive and requires freezing a process. This is why we
> want to maximize the load that we can carry on for each iteration.
Honestly, it sounds like what you want is just process_vm_readv().
The pipe part sounds like a horrible hacky thing.
I also assume you already tried that, and hit some performance issues.
But it does sound like the better interface, more directly what you
want.
So what are the problems with using process_vm_readv?
Linus
Powered by blists - more mailing lists