All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Jonathan Brassow <jbrassow@redhat.com>
Cc: dm-devel@redhat.com, dmzhang@suse.de
Subject: Re: dm-log-userspace: Allow mark requests to piggyback on flush requests
Date: Mon, 13 Jan 2014 21:59:37 -0500	[thread overview]
Message-ID: <20140114025937.GA5816@redhat.com> (raw)
In-Reply-To: <1389666600.12232.2.camel@f16>

On Mon, Jan 13 2014 at  9:30pm -0500,
Jonathan Brassow <jbrassow@redhat.com> wrote:

> dm-log-userspace: Allow mark requests to piggyback on flush requests
> 
> In the cluster evironment, cluster write has poor performance.
> Because userspace_flush has to contact userspace program(cmirrord)
> in clear/mark/flush request. But both mark and flush requests
> require cmirrord to circle message to all the cluster nodes in each
> flush call.  This behave is realy slow. So the idea is merging
> mark and flush request together to reduce the kernel-userspace-kernel
> time.  Allow a new directive, "integrated_flush" that can be used to
> instruct the kernel log code to combine flush and mark requests when
> directed by userspace.  Additionlly, flush requests are performed
> lazily when only clear requests exist.
> 
> Signed-off-by: dongmao zhang <dmzhang@suse.com>
> Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>

Hey Jon,

Thanks for following through with this.  Should it be attributed to
dongmao as the author?

  reply	other threads:[~2014-01-14  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  2:30 [PATCH] dm-log-userspace: Allow mark requests to piggyback on flush requests Jonathan Brassow
2014-01-14  2:59 ` Mike Snitzer [this message]
2014-01-14  4:08   ` Brassow Jonathan
2014-01-15 21:45 ` [PATCH] " Brassow Jonathan

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=20140114025937.GA5816@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=dmzhang@suse.de \
    --cc=jbrassow@redhat.com \
    /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.