[lkml]   [2018]   [Oct]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2] mm: Introduce new function vm_insert_kmem_page
Hi Souptick,

On Thu, Oct 4, 2018 at 8:49 PM Souptick Joarder <> wrote:
> On Thu, Oct 4, 2018 at 11:47 PM Matthew Wilcox <> wrote:
> >
> > I think this is a bad plan. What we should rather do is examine the current
> > users of vm_insert_page() and ask "What interface would better replace
> > vm_insert_page()?"
> >
> > As I've said to you before, I believe the right answer is to have a
> > vm_insert_range() which takes an array of struct page pointers. That
> > fits the majority of remaining users.
> Ok, but it will take some time.
> Is it a good idea to introduce the final vm_fault_t patch and then
> start working on vm_insert_range as it will be bit time consuming ?

Well, why is there a rush? Development should be done in a patch
series or a tree, and submitted as a whole, instead of sending partial

Also, not sure if you saw my comments/review: if the interface is not
going to change, why the name change? Why can't we simply keep using


 \ /
  Last update: 2018-10-04 21:46    [W:0.132 / U:8.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site