linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Vasily Averin <vvs@virtuozzo.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse: redundant get_fuse_inode() calls in fuse_writepages_fill()
Date: Thu, 3 Oct 2019 10:21:02 +0200	[thread overview]
Message-ID: <CAJfpegtSLNBHDSTEm9aRhi2J+8JNPnZjcBBB_j5cjA6NtqZZOg@mail.gmail.com> (raw)
In-Reply-To: <c09509ef-982e-d4bd-ed0b-da8389a7d066@virtuozzo.com>

On Mon, Aug 19, 2019 at 7:48 AM Vasily Averin <vvs@virtuozzo.com> wrote:
>
> Currently fuse_writepages_fill() calls get_fuse_inode() few times with
> the same argument.

Thanks, applied.

Miklos

      reply	other threads:[~2019-10-03  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19  5:48 [PATCH] fuse: redundant get_fuse_inode() calls in fuse_writepages_fill() Vasily Averin
2019-10-03  8:21 ` Miklos Szeredi [this message]

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=CAJfpegtSLNBHDSTEm9aRhi2J+8JNPnZjcBBB_j5cjA6NtqZZOg@mail.gmail.com \
    --to=miklos@szeredi.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vvs@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).