From qemu-devel Fri Mar 09 10:53:31 2012 From: Stefan Hajnoczi Date: Fri, 09 Mar 2012 10:53:31 +0000 To: qemu-devel Subject: Re: [Qemu-devel] [RFC PATCH 14/17] block: support FALLOC_FL_PUNCH_HOLE trimming Message-Id: X-MARC-Message: https://marc.info/?l=qemu-devel&m=133129047222131 On Fri, Mar 9, 2012 at 10:43 AM, Paolo Bonzini wrote: > Il 09/03/2012 11:31, Stefan Hajnoczi ha scritto: >>> > +#ifdef FALLOC_FL_PUNCH_HOLE >>> > + =A0 =A0retval =3D fallocate(s->fd, FALLOC_FL_PUNCH_HOLE|FALLOC_FL_K= EEP_SIZE, >>> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 sector_num << 9, (int64= _t)nb_sectors << 9); >> I'm concerned about introducing blocking syscalls in coroutine code >> paths. =A0This needs to be done asynchronously. > > Right; it is no worse than what is already there, except that XFS could > use paio_ioctl. =A0Alternatives are: It is worse in the sense that if you make this feature more widely available then it deserves a production-quality implementation. > 1) require a new-enough kernel and only use fallocate; return a NULL > aiocb if !has_discard and convert it to ENOTSUP. > > 2) extract now from my threads branch the work to generalize > posix-aio-compat into a more flexible threadpool, and move the AIO code > back to block/raw-posix.c. 3) Add discard to posix-aio-compat.c as an AIO request? Stefan