All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Niels de Vos <ndevos@redhat.com>
Cc: qemu-block@nongnu.org, integration@gluster.org,
	qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/2] gluster: the glfs_io_cbk callback function pointer adds pre/post stat args
Date: Tue, 5 Mar 2019 11:29:34 +0100	[thread overview]
Message-ID: <20190305102934.GD5280@dhcp-200-226.str.redhat.com> (raw)
In-Reply-To: <20190304162103.18912-3-ndevos@redhat.com>

Am 04.03.2019 um 17:21 hat Niels de Vos geschrieben:
> The glfs_*_async() functions do a callback once finished. This callback
> has changed its arguments, pre- and post-stat structures have been
> added. This makes it possible to improve cashing, which is useful for

Did you mean "caching"?

> Samba and NFS-Ganesha, but not so much for QEMU. Gluster 6 is the first
> release that includes these new arguments.
> 
> With an additional detection in ./configure, the new arguments can
> conditionally get included in the glfs_io_cbk handler.
> 
> Signed-off-by: Niels de Vos <ndevos@redhat.com>

Kevin

  reply	other threads:[~2019-03-05 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 16:21 [Qemu-devel] [PATCH 0/2] block: Gluster 6 compatibility Niels de Vos
2019-03-04 16:21 ` [Qemu-devel] [PATCH 1/2] block/gluster: Handle changed glfs_ftruncate signature Niels de Vos
2019-03-04 16:41   ` Daniel P. Berrangé
2019-03-05 15:16     ` Niels de Vos
2019-03-04 16:21 ` [Qemu-devel] [PATCH 2/2] gluster: the glfs_io_cbk callback function pointer adds pre/post stat args Niels de Vos
2019-03-05 10:29   ` Kevin Wolf [this message]
2019-03-05 15:18     ` [Qemu-devel] [Qemu-block] " Niels de Vos

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=20190305102934.GD5280@dhcp-200-226.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=integration@gluster.org \
    --cc=ndevos@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.