From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] Refactor aiocp using new LTP API
Date: Tue, 2 Aug 2022 16:30:28 +0200 [thread overview]
Message-ID: <Yuk1BC/gsYb8tzBh@yuki> (raw)
In-Reply-To: <d0cf0e1f-8e0c-127c-b613-ac8b3bd99ad6@suse.com>
Hi!
> I think that check doesn't make much sense and we probably should stuck
> to "n = aionum - busy",
> since that's the value we always need to allocate since became free in
> the previous loop iteration.
I guess MIN(aionum-busy, tocopy) or something like this since we want to
avoid schedulling reads past the end of the file.
> >> + aio_blksize = 64 * 1024;
> >> + filesize = 1 * 1024 * 1024;
> >> + aionum = 16;
> >> + srcflags = O_RDONLY;
> >> + dstflags = O_WRONLY;
> > Can we just initialize the globals directly instead of here in the test
> > setup()?
> In the last ltp-aiodio tests, we decided to initialize global variables
> inside setup().
Wasn't it exactly the other way around?
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-08-02 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 15:14 [LTP] [PATCH v2] Refactor aiocp using new LTP API Andrea Cervesato via ltp
2022-08-02 13:08 ` Cyril Hrubis
2022-08-02 14:12 ` Andrea Cervesato via ltp
2022-08-02 14:30 ` Cyril Hrubis [this message]
2022-08-02 14:30 ` Andrea Cervesato via ltp
2022-08-03 4:47 ` Petr Vorel
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 15:18 [LTP] [PATCH v3] " Andrea Cervesato via ltp
2022-08-03 4:52 ` [LTP] [PATCH v2] " Petr Vorel
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=Yuk1BC/gsYb8tzBh@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