From: Jens Axboe <axboe@kernel.dk>
To: castor.fu@egocast.org, fio@vger.kernel.org
Cc: Castor Fu <castor@alumni.caltech.edu>
Subject: Re: [PATCH 2/2] Add unlink hook to ioengine API
Date: Fri, 21 Mar 2014 09:27:08 -0600 [thread overview]
Message-ID: <532C5A4C.7020501@kernel.dk> (raw)
In-Reply-To: <1395338370-89038-3-git-send-email-castor.fu@egocast.org>
On 03/20/2014 11:59 AM, castor.fu@egocast.org wrote:
> From: Castor Fu <castor@alumni.caltech.edu>
>
> ---
> filesetup.c | 6 +++---
> ioengine.h | 4 +++-
> ioengines.c | 8 ++++++++
> iolog.c | 2 +-
> 4 files changed, 15 insertions(+), 5 deletions(-)
This patch seems a bit pointless, without wiring some IO engine up for
an unlink hook that isn't unlink(2).
--
Jens Axboe
next prev parent reply other threads:[~2014-03-21 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:02 unlink=1 issue on Windows Sébastien Bouchex Bellomié
2014-03-20 14:29 ` Jens Axboe
2014-03-20 17:59 ` unlink castor.fu
2014-03-20 17:59 ` [PATCH 1/2] Pass -Wstrict-prototypes -Wold-style-definition, whitespace castor.fu
2014-03-21 15:29 ` Jens Axboe
2014-03-20 17:59 ` [PATCH 2/2] Add unlink hook to ioengine API castor.fu
2014-03-21 15:27 ` Jens Axboe [this message]
2014-03-21 17:03 ` Castor Fu
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=532C5A4C.7020501@kernel.dk \
--to=axboe@kernel.dk \
--cc=castor.fu@egocast.org \
--cc=castor@alumni.caltech.edu \
--cc=fio@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