All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Marshall <hubcap@omnibond.com>
To: David Howells <dhowells@redhat.com>, Mike Marshall <hubcap@omnibond.com>
Cc: Matthew Wilcox <willy@infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC PATCH v2] implement orangefs_readahead
Date: Fri, 16 Apr 2021 10:36:52 -0400	[thread overview]
Message-ID: <CAOg9mSSxZUwZ0-OdCfb7gLgETkCJOd-9PCrpqWwzqXffwMSejA@mail.gmail.com> (raw)
In-Reply-To: <1268214.1618326494@warthog.procyon.org.uk>

Hi David...

I got your netfs-lib branch as of Apr 15.

I added my orangefs_readahead on top of it and ran through
xfstests. I failed generic 75, 112, 127, & 263, which I
don't usually fail.

I took off my orangefs_readahead patch and ran xfstests with
your untouched netfs-lib branch. No regressions.

I git-reset back to 5.12.0-rc4 (I think your netfs-lib branch is based
on a linus-tree-of-the-day?) and ran xfstests... no regressions.

So... I think all your stuff is working well from my perspective
and that I need to figure out why my orangefs_readahead patch
is causing the regressions I listed. My readahead implementation (via your
readahead_expand) is really fast, but it is bare-bones... I'm probably
leaving out some important stuff... I see other filesystem's
readahead implementations doing stuff like avoiding doing readahead
on pages that have yet to be written back for example.

The top two commits at https://github.com/hubcapsc/linux/tree/readahead_v3
is the current state of my readahead implementation.

Please do add
Tested-by: Mike Marshall <hubcap@omnibond.com>

-Mike

On Tue, Apr 13, 2021 at 11:08 AM David Howells <dhowells@redhat.com> wrote:
>
> Mike Marshall <hubcap@omnibond.com> wrote:
>
> > Hi David... I've been gone on a motorcycle adventure,
> > sorry for the delay... here's my public branch...
> >
> > https://github.com/hubcapsc/linux/tree/readahead_v3
>
> That seems to have all of my fscache-iter branch in it.  I thought you'd said
> you'd dropped them because they were causing problems.
>
> Anyway, I've distilled the basic netfs lib patches, including the readahead
> expansion patch and ITER_XARRAY patch here:
>
>         https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-lib
>
> if that's of use to you?
>
> If you're using any of these patches, would it be possible to get a Tested-by
> for them that I can add?
>
> David
>

  reply	other threads:[~2021-04-16 14:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 22:25 [RFC PATCH] implement orangefs_readahead Mike Marshall
2021-02-01 13:08 ` Matthew Wilcox
2021-02-02  3:32   ` Mike Marshall
2021-03-13 15:31     ` [RFC PATCH v2] " Mike Marshall
2021-03-17  3:04       ` Mike Marshall
2021-03-24 11:10     ` David Howells
2021-03-27  2:55       ` Mike Marshall
2021-03-27  3:50         ` Matthew Wilcox
2021-03-27  8:31         ` David Howells
2021-03-27 13:56           ` Matthew Wilcox
2021-03-27 15:40             ` Mike Marshall
2021-03-27 15:56               ` Matthew Wilcox
2021-03-28  3:04                 ` Mike Marshall
2021-03-29  1:51                   ` Mike Marshall
2021-03-29  9:37                   ` David Howells
2021-03-29 23:25                     ` Mike Marshall
     [not found]                       ` <3726695.1617284551@warthog.procyon.org.uk >
2021-04-13 15:08                         ` David Howells
2021-04-16 14:36                           ` Mike Marshall [this message]
2021-04-16 15:14                             ` Matthew Wilcox
2021-04-25  1:51                               ` Mike Marshall
2021-04-16 15:41                           ` David Howells
2021-04-25  1:43                             ` Mike Marshall
2021-04-25  7:49                             ` David Howells
2021-04-26 14:53                               ` Mike Marshall
2021-04-26 19:01                                 ` Mike Marshall
2021-04-26 20:01                                 ` David Howells
2021-04-26  8:37                             ` David Howells
2021-04-01 13:42                     ` David Howells
2021-04-08 20:39                       ` Mike Marshall

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=CAOg9mSSxZUwZ0-OdCfb7gLgETkCJOd-9PCrpqWwzqXffwMSejA@mail.gmail.com \
    --to=hubcap@omnibond.com \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.