All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
	dm-devel@redhat.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: [git pull] device mapper changes for 4.18
Date: Mon, 4 Jun 2018 17:13:44 -0400	[thread overview]
Message-ID: <20180604211343.GB6079@redhat.com> (raw)
In-Reply-To: <20180604195858.GD12217@hirez.programming.kicks-ass.net>

On Mon, Jun 04 2018 at  3:58pm -0400,
Peter Zijlstra <peterz@infradead.org> wrote:

> On Mon, Jun 04, 2018 at 12:39:11PM -0700, Linus Torvalds wrote:
> > On Mon, Jun 4, 2018 at 12:37 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > Would it help if we did s/swake_up/swake_up_one/g ?
> > >
> > > Then there would not be an swake_up() to cause confusion.
> > 
> > Yes, i think that would already be a big improvement, forcing people
> > to be aware of the exclusive nature.
> 
> The below will of course conflict with the merge request under
> discussion. Also completely untested.

No worries there since I'll be resubmitting dm-writecache for 4.19.

(Mikulas would like to still use swait for the dm-writecache's endio
thread, since endio_thread_wait only has a single waiter.  I told him to
convert the other 2, benchmark it with still swait in endio path, then
convert the one used in endio, benchmark will all converted and we'd
revisit if there is a compelling performance difference.  But even then
I'm not sure I want DM on the list of swait consumers... to be
continued)

  parent reply	other threads:[~2018-06-04 21:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 15:32 [git pull] device mapper changes for 4.18 Mike Snitzer
2018-06-04 18:54 ` Linus Torvalds
2018-06-04 19:09   ` Mike Snitzer
2018-06-04 19:29     ` Linus Torvalds
2018-06-04 19:36       ` Peter Zijlstra
2018-06-04 19:39         ` Linus Torvalds
2018-06-04 19:58           ` Peter Zijlstra
2018-06-04 20:40             ` Linus Torvalds
2018-06-04 21:13             ` Mike Snitzer [this message]
2018-06-04 21:22               ` Linus Torvalds
2018-06-04 21:53                 ` Mikulas Patocka
2018-06-04 22:16                   ` Linus Torvalds
2018-06-05  8:59                     ` Peter Zijlstra
2018-06-05 15:53                       ` Linus Torvalds
2018-06-11 19:41     ` [git pull v2] " Mike Snitzer
2018-06-04 19:09   ` [git pull] " Linus Torvalds

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=20180604211343.GB6079@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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.