reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: [RFC] [PATCH 0/2] libaal: add device "discard" operation.
Date: Fri, 09 May 2014 00:03:08 +0200	[thread overview]
Message-ID: <536BFF1C.5040103@gmail.com> (raw)
In-Reply-To: <1399576404-5527-1-git-send-email-intelfx100@gmail.com>

Great, thank you!

To our shame, reiser4 neither preallocates, nor punches holes.
TBH, too lazy ;) I prefer to concentrate on features, which are
either unique, or perform better in reiser4 (like discard)...

Thanks,
Edward.


On 05/08/2014 09:13 PM, Ivan Shapovalov wrote:
> This implements device discard functionality in libaal to be used
> by mkfs and friends.
>
> Note that the build system is _not_ regenerated, so the direct result of
> applying these patches won't build.
>
> Ivan Shapovalov (2):
>    configure.in: check for fallocate() and related headers.
>    Add aal_device_discard() function and implement it for file-based
>      device.
>
>   configure.in         |  4 +--
>   include/aal/device.h |  4 +++
>   include/aal/types.h  |  3 +++
>   src/device.c         | 15 +++++++++++
>   src/file.c           | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>   5 files changed, 98 insertions(+), 2 deletions(-)
>


      parent reply	other threads:[~2014-05-08 22:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 19:13 [RFC] [PATCH 0/2] libaal: add device "discard" operation Ivan Shapovalov
2014-05-08 19:13 ` [RFC] [PATCH 1/2] configure.in: check for fallocate() and related headers Ivan Shapovalov
2014-05-08 19:13 ` [RFC] [PATCH 2/2] Add aal_device_discard() function and implement it for file-based device Ivan Shapovalov
2014-05-08 22:03 ` Edward Shishkin [this message]

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=536BFF1C.5040103@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=intelfx100@gmail.com \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).