All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dai Ngo <dai.ngo@oracle.com>
To: olga.kornievskaia@gmail.com
Cc: linux-nfs@vger.kernel.org, trondmy@hammerspace.com,
	bfields@fieldses.org, chuck.lever@oracle.com
Subject: [PATCH v2 0/2] enhance NFSv4.2 SSC to delay unmount source's export.
Date: Fri,  2 Apr 2021 19:30:29 -0400	[thread overview]
Message-ID: <20210402233031.36731-1-dai.ngo@oracle.com> (raw)

Hi,

Currently the source's export is mounted and unmounted on every
inter-server copy operation. This causes unnecessary overhead
for each copy.

This patch series is an enhancement to allow the export to remain
mounted for a configurable period (default to 15 minutes). If the 
export is not being used for the configured time it will be unmounted
by a delayed task. If it's used again then its expiration time is
extended for another period.

Since mount and unmount are no longer done on each copy request,
this overhead is no longer used to decide whether the copy should
be done with inter-server copy or generic copy. The threshold used
to determine sync or async copy is now used for this decision.

-Dai

v2: fix compiler warning of missing prototype.



             reply	other threads:[~2021-04-02 23:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 23:30 Dai Ngo [this message]
2021-04-02 23:30 ` [PATCH v2 1/2] NFSD: delay unmount source's export after inter-server copy completed Dai Ngo
2021-04-02 23:30 ` [PATCH v2 2/2] NFSv4.2: mount overhead should not be used as threshold for inter-server copy Dai Ngo
2021-04-06 16:33 ` [PATCH v2 0/2] enhance NFSv4.2 SSC to delay unmount source's export Chuck Lever III
2021-04-06 19:41   ` Olga Kornievskaia
2021-04-06 19:42     ` Chuck Lever III
2021-04-06 19:57       ` Olga Kornievskaia
2021-04-06 19:58         ` Chuck Lever III
2021-04-06 20:43           ` Olga Kornievskaia
2021-04-07  1:12             ` dai.ngo
2021-04-07  1:23               ` dai.ngo
     [not found]                 ` <CAN-5tyGS0ZO4PtTseLSmC4=fYQCUwMs6FB509g2PSCg1v+jySg@mail.gmail.com>
2021-04-07 17:13                   ` dai.ngo
2021-04-07 19:01                     ` Olga Kornievskaia
2021-04-07 20:16                       ` dai.ngo
2021-04-07 21:40                         ` Olga Kornievskaia
2021-04-07 22:50                           ` dai.ngo
2021-04-08  0:58                             ` Olga Kornievskaia
2021-04-08  7:19                               ` dai.ngo
2021-04-08 15:25                               ` Chuck Lever III
2021-04-06 19:58         ` dai.ngo

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=20210402233031.36731-1-dai.ngo@oracle.com \
    --to=dai.ngo@oracle.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=olga.kornievskaia@gmail.com \
    --cc=trondmy@hammerspace.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 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.