All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org, virtio-fs@redhat.com,
	dan.j.williams@intel.com
Cc: vgoyal@redhat.com, willy@infradead.org, jack@suse.cz, groug@kaod.org
Subject: [PATCH v6 0/3] dax: Fix missed wakeup in put_unlocked_entry()
Date: Wed, 28 Apr 2021 15:03:11 -0400	[thread overview]
Message-ID: <20210428190314.1865312-1-vgoyal@redhat.com> (raw)

Hi,

This is V6. Only change since V5 is that I changed order of WAKE_NEXT
and WAKE_ALL in comments too.

Vivek

Vivek Goyal (3):
  dax: Add an enum for specifying dax wakup mode
  dax: Add a wakeup mode parameter to put_unlocked_entry()
  dax: Wake up all waiters after invalidating dax entry

 fs/dax.c | 35 +++++++++++++++++++++++------------
 1 file changed, 23 insertions(+), 12 deletions(-)

-- 
2.25.4


WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org, virtio-fs@redhat.com,
	dan.j.williams@intel.com
Cc: willy@infradead.org, jack@suse.cz, groug@kaod.org
Subject: [PATCH v6 0/3] dax: Fix missed wakeup in put_unlocked_entry()
Date: Wed, 28 Apr 2021 15:03:11 -0400	[thread overview]
Message-ID: <20210428190314.1865312-1-vgoyal@redhat.com> (raw)

Hi,

This is V6. Only change since V5 is that I changed order of WAKE_NEXT
and WAKE_ALL in comments too.

Vivek

Vivek Goyal (3):
  dax: Add an enum for specifying dax wakup mode
  dax: Add a wakeup mode parameter to put_unlocked_entry()
  dax: Wake up all waiters after invalidating dax entry

 fs/dax.c | 35 +++++++++++++++++++++++------------
 1 file changed, 23 insertions(+), 12 deletions(-)

-- 
2.25.4
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org, virtio-fs@redhat.com,
	dan.j.williams@intel.com
Cc: jack@suse.cz, willy@infradead.org, vgoyal@redhat.com
Subject: [Virtio-fs] [PATCH v6 0/3] dax: Fix missed wakeup in put_unlocked_entry()
Date: Wed, 28 Apr 2021 15:03:11 -0400	[thread overview]
Message-ID: <20210428190314.1865312-1-vgoyal@redhat.com> (raw)

Hi,

This is V6. Only change since V5 is that I changed order of WAKE_NEXT
and WAKE_ALL in comments too.

Vivek

Vivek Goyal (3):
  dax: Add an enum for specifying dax wakup mode
  dax: Add a wakeup mode parameter to put_unlocked_entry()
  dax: Wake up all waiters after invalidating dax entry

 fs/dax.c | 35 +++++++++++++++++++++++------------
 1 file changed, 23 insertions(+), 12 deletions(-)

-- 
2.25.4


             reply	other threads:[~2021-04-28 19:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 19:03 Vivek Goyal [this message]
2021-04-28 19:03 ` [Virtio-fs] [PATCH v6 0/3] dax: Fix missed wakeup in put_unlocked_entry() Vivek Goyal
2021-04-28 19:03 ` Vivek Goyal
2021-04-28 19:03 ` [PATCH v6 1/3] dax: Add an enum for specifying dax wakup mode Vivek Goyal
2021-04-28 19:03   ` [Virtio-fs] " Vivek Goyal
2021-04-28 19:03   ` Vivek Goyal
2021-04-28 19:03 ` [PATCH v6 2/3] dax: Add a wakeup mode parameter to put_unlocked_entry() Vivek Goyal
2021-04-28 19:03   ` [Virtio-fs] " Vivek Goyal
2021-04-28 19:03   ` Vivek Goyal
2021-04-28 19:03 ` [PATCH v6 3/3] dax: Wake up all waiters after invalidating dax entry Vivek Goyal
2021-04-28 19:03   ` [Virtio-fs] " Vivek Goyal
2021-04-28 19:03   ` Vivek Goyal
2021-04-28 21:08 ` [PATCH v6 0/3] dax: Fix missed wakeup in put_unlocked_entry() Dan Williams
2021-04-28 21:08   ` [Virtio-fs] " Dan Williams
2021-04-28 21:08   ` Dan Williams

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=20210428190314.1865312-1-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=groug@kaod.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=virtio-fs@redhat.com \
    --cc=willy@infradead.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.