From: John Cavan <john.cavan@sympatico.ca>
To: "Juan J. Quintela" <quintela@fi.udc.es>
Cc: trond.myklebust@fys.uio.no,
Linus Torvalds <torvalds@transmeta.com>,
linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: PATCH: rewrite of invalidate_inode_pages
Date: Fri, 12 May 2000 07:28:45 -0400 [thread overview]
Message-ID: <391BEAED.C9313263@sympatico.ca> (raw)
In-Reply-To: <ytt1z38acqg.fsf@vexeta.dc.fi.udc.es>
I'm by no means an expert in this, I just follow the list to learn, but
would it not be possible to make ITERATIONS count a runtime configurable
parameter in the /proc filesystem that defaults to 100? That would allow
for the best tuning scenario for a given system.
Just a thought.
John Cavan
"Juan J. Quintela" wrote:
>
> >>>>> "trond" == Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>
> >>>>> " " == Juan J Quintela <quintela@fi.udc.es> writes:
> >> Then you want only invalidate the non_locked pages: do you
>
> trond> That's right. This patch looks much more appropriate.
>
> >> + while (count == ITERATIONS) {
> >> + spin_lock(&pagecache_lock);
> >> + spin_lock(&pagemap_lru_lock);
> >> + head = &inode->i_mapping->pages;
> >> + curr = head->next;
> >> + count = 0;
> >> +
> >> + while ((curr != head) && (count++ < ITERATIONS)) {
>
> trond> Just one question: Isn't it better to do it all in 1 iteration through
> trond> the loop rather than doing it in batches of 100 pages?
> trond> You can argue that you're freeing up the spinlocks for the duration of
> trond> the loop_and_test, but is that really going to make a huge difference
> trond> to SMP performance?
>
> Trond, I have not an SMP machine (yet), and I can not tell you numbers
> now. I put the counter there to show that we *may* want to limit the
> latency there. I am thinking in the write of a big file, that can
> take a lot to free all the pages, but I don't know, *you* are the NFS
> expert, this was one of the reasons that we want feedback from the
> users of the call. (You have been very good giving comments).
>
> My idea to put a limit is to put a limit than normally you do all in
> one iteration, but in the exceptional case of a big amount of pages,
> the latency is limited. There is a limit in the number of pages that
> can be in that list?
>
> 100 is one number that can need tuning, I don't know. SMP experts
> anywhere?
>
> By the way, while we are here, the only difference between
> truncate_inode_pages and invalidate_inode_pages is the one that you
> told here before? I am documenting some of the MM stuff, and your
> comments in that aspect are really wellcome. (You will have noted
> now that I am quite newbie here).
>
> Later, Juan.
>
> --
> In theory, practice and theory are the same, but in practice they
> are different -- Larry McVoy
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-05-12 11:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 21:40 Juan J. Quintela
2000-05-11 21:47 ` Linus Torvalds
2000-05-11 21:56 ` Juan J. Quintela
2000-05-11 22:22 ` Linus Torvalds
2000-05-12 1:01 ` Juan J. Quintela
2000-05-12 2:02 ` PATCH: new page_cache_get() (try 2) Juan J. Quintela
2000-05-11 22:22 ` PATCH: rewrite of invalidate_inode_pages Ingo Molnar
2000-05-11 22:34 ` Trond Myklebust
2000-05-11 22:54 ` Juan J. Quintela
2000-05-11 23:17 ` Trond Myklebust
2000-05-11 23:28 ` Juan J. Quintela
2000-05-11 23:55 ` Trond Myklebust
2000-05-12 11:28 ` John Cavan [this message]
2000-05-12 11:37 ` Juan J. Quintela
2000-05-12 12:51 ` Trond Myklebust
2000-05-12 13:21 ` Arjan van de Ven
2000-05-12 13:35 ` Trond Myklebust
2000-05-12 17:57 ` Juan J. Quintela
2000-05-12 13:30 ` Juan J. Quintela
2000-05-11 22:05 ` Jeff V. Merkey
2000-05-11 22:28 ` Trond Myklebust
2000-05-11 22:43 ` Juan J. Quintela
2000-05-11 22:56 ` Trond Myklebust
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=391BEAED.C9313263@sympatico.ca \
--to=john.cavan@sympatico.ca \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=quintela@fi.udc.es \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
/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