From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6] Refactor aiocp using new LTP API
Date: Wed, 10 Aug 2022 14:37:29 +0200 [thread overview]
Message-ID: <YvOmiXBO1njKMzUM@yuki> (raw)
In-Reply-To: <ade189ba-4211-99a8-d5e6-c99b1950e21b@suse.com>
Hi!
> Yes, we can reduce the amount of time to generate file (especially if
> it's really big), but I wouldn't
> introduce any repetition because we would like to check that file has
> been copied properly during
> callbacks which are asynchronous by definition.
I guess that we can do a little trick such as making the buffer with
random data slightly bigger and choosing a random start offset in that
etc.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-10 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 9:28 [LTP] [PATCH v6] Refactor aiocp using new LTP API Andrea Cervesato via ltp
2022-08-10 10:37 ` Cyril Hrubis
2022-08-10 12:28 ` Andrea Cervesato via ltp
2022-08-10 12:37 ` Cyril Hrubis [this message]
2022-08-11 9:42 ` Petr Vorel
2022-08-11 10:25 ` Cyril Hrubis
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=YvOmiXBO1njKMzUM@yuki \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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