public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Catherine Hoang <catherine.hoang@oracle.com>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>
Subject: Re: proposal: enhance 'cp --reflink' to expose ioctl_ficlonerange
Date: Tue, 19 Sep 2023 10:31:53 +0700	[thread overview]
Message-ID: <ZQkWKdkHTZXU_fHN@debian.me> (raw)
In-Reply-To: <8911B94D-DD29-4D6E-B5BC-32EAF1866245@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

On Tue, Sep 19, 2023 at 02:43:32AM +0000, Catherine Hoang wrote:
> - Write a test case that performs a FICLONERANGE2 copy with a time budget.
>   If our implementation allows FICLONERANGE2 to be restarted after a signal
>   interruption, we can test this by creating a loop and setting up a signal
>   via alarm(2) or timer_create(2).
> - Write a test case that generates a file with many extents and tests that
>   the kernel exits with partial completion when given a very short time budget.

For the actual tests, what are selected time budgets that are to be
implemented in the test?

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-09-19  3:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  2:43 proposal: enhance 'cp --reflink' to expose ioctl_ficlonerange Catherine Hoang
2023-09-19  3:31 ` Bagas Sanjaya [this message]
2023-09-19  5:51 ` Dave Chinner
2023-09-20  0:00   ` Darrick J. Wong
2023-09-20  1:07     ` Dave Chinner
2023-09-21 22:26       ` Darrick J. Wong
2023-09-21 23:18         ` Dave Chinner
2023-09-25 21:28           ` Darrick J. Wong
2023-09-26 21:18             ` Catherine Hoang

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=ZQkWKdkHTZXU_fHN@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=catherine.hoang@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox