linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/2] pagevec: Allow pagevecs to be different sizes
Date: Fri, 6 Nov 2020 14:18:40 -0800	[thread overview]
Message-ID: <400d19a9-1113-5903-053e-85100104d229@linux.intel.com> (raw)
In-Reply-To: <20201106191210.GR17076@casper.infradead.org>



On 11/6/20 11:12 AM, Matthew Wilcox wrote:
 
> 
> I have a number of changes already in that area that are currently in-flight.
> 
> https://lore.kernel.org/linux-mm/20201026041408.25230-1-willy@infradead.org/
> 
> (although I should modify patch 9/12 to not use PAGEVEC_SIZE directly)

Okay. I assume that you are using pagevec_size somewhere to replace those
hardcoded PAGEVEC_SIZE somewhere.

> 
> I have some patches that I haven't bothered sending yet since I have so
> many other outstanding patches to do something similar to find_get_pages()
> / find_get_pages_range() / pagevec_lookup() / pagevec_lookup_range().
> 
> 
> The trace you sent showed the problem being with the lru_add pagevec,
> and that's never used with the pagevec_lookup_* APIs (afaik), so I didn't
> see it as urgent to fix those.
> 

Okay.

Thanks for allowing the bigger pagevec size tweak in your patches.

Tim


  reply	other threads:[~2020-11-06 22:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 17:26 [PATCH 0/2] Increase the size of LRU pagevecs Matthew Wilcox (Oracle)
2020-11-05 17:26 ` [PATCH 1/2] pagevec: Allow pagevecs to be different sizes Matthew Wilcox (Oracle)
2020-11-06 17:17   ` Tim Chen
2020-11-06 19:12     ` Matthew Wilcox
2020-11-06 22:18       ` Tim Chen [this message]
2020-11-07  1:21         ` Matthew Wilcox
2020-11-05 17:26 ` [PATCH 2/2] pagevec: Increase the size of LRU pagevecs Matthew Wilcox (Oracle)
2020-11-06  0:51 ` [PATCH 0/2] " Tim Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=400d19a9-1113-5903-053e-85100104d229@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=jack@suse.cz \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox