From: Christoph Hellwig <hch@lst.de>
To: Philippe Liard <pliard@google.com>
Cc: Christoph Hellwig <hch@lst.de>,
phillip@squashfs.org.uk, linux-kernel@vger.kernel.org,
groeck@chromium.org, akpm@linux-foundation.org
Subject: Re: [PATCH v3] squashfs: Migrate from ll_rw_block usage to BIO
Date: Wed, 8 Apr 2020 08:24:15 +0200 [thread overview]
Message-ID: <20200408062415.GA25951@lst.de> (raw)
In-Reply-To: <CAEThQxfKWGo1TZ7SZ-N6kizbkujWwu3yKXUGDrsVrGjtopVqkA@mail.gmail.com>
On Fri, Apr 03, 2020 at 10:37:15AM +0900, Philippe Liard wrote:
> This is lower priority for us now but I agree that it would be good to land it.
> This is my first patch being approved so I'm not familiar with the next steps.
> Can you land it yourself or is there something more that I should do?
Normally Phillip should pick it up as the squashfs maintainer, but he
has been last active about a year and a half ago.
Andrew, is this something you could pick up through the linux-mm tree?
>
>
> On Fri, Apr 3, 2020 at 12:35 AM Christoph Hellwig <hch@lst.de> wrote:
> >
> > On Fri, Nov 15, 2019 at 10:20:33AM +0900, Philippe Liard wrote:
> > > On Wed, Nov 6, 2019 at 6:28 PM Philippe Liard <pliard@google.com> wrote:
> > > >
> > > > On Wed, Nov 6, 2019 at 5:37 PM Christoph Hellwig <hch@lst.de> wrote:
> > > > >
> > > > > Sorry for the empty reply.
> > > > >
> > > > > This was meant to say that the patch looks good to me:
> > > > >
> > > > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > > >
> > > > Thanks!
> > >
> > > FYI I'm unfortunately no longer observing the 40% impact announced in the
> > > commit description after many optimizations landed in the Chrome OS VM
> > > infrastructure.
> > >
> > > Hopefully moving to BIO is still desirable though. Thank you in any case for
> > > your help/guidance and all the time you spent reviewing this.
> >
> > Do you still plan to submit the patch? I think it is a major cleanup
> > of the codebase, so I'd like to see it land.
---end quoted text---
next prev parent reply other threads:[~2020-04-08 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 7:42 [PATCH v3] squashfs: Migrate from ll_rw_block usage to BIO Philippe Liard
2019-11-06 8:34 ` Christoph Hellwig
2019-11-06 8:37 ` Christoph Hellwig
2019-11-06 9:28 ` Philippe Liard
2019-11-15 1:20 ` Philippe Liard
2020-04-02 15:35 ` Christoph Hellwig
2020-04-03 1:37 ` Philippe Liard
2020-04-08 6:24 ` Christoph Hellwig [this message]
2020-04-09 0:38 ` Andrew Morton
2020-04-09 15:55 ` Guenter Roeck
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=20200408062415.GA25951@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@squashfs.org.uk \
--cc=pliard@google.com \
/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