NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	 "dan.j.williams\@intel.com" <dan.j.williams@intel.com>,
	 "vishal.l.verma\@intel.com" <vishal.l.verma@intel.com>,
	 "dave.jiang\@intel.com" <dave.jiang@intel.com>,
	 "ira.weiny\@intel.com" <ira.weiny@intel.com>,
	 "nvdimm\@lists.linux.dev" <nvdimm@lists.linux.dev>,
	 axboe@kernel.dk,  linux-block@vger.kernel.org
Subject: Re: [PATCH V2 1/1] pmem: set QUEUE_FLAG_NOWAIT
Date: Wed, 02 Aug 2023 11:27:12 -0400	[thread overview]
Message-ID: <x49o7jpv50v.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20230802123010.GB30792@lst.de> (Christoph Hellwig's message of "Wed, 2 Aug 2023 14:30:10 +0200")

Christoph Hellwig <hch@lst.de> writes:

> Given that pmem simply loops over an arbitrarily large bio I think
> we also need a threshold for which to allow nowait I/O.  While it
> won't block for giant I/Os, doing all of them in the submitter
> context isn't exactly the idea behind the nowait I/O.
>
> I'm not really sure what a good theshold would be, though.

There's no mention of the latency of the submission side in the
documentation for RWF_NOWAIT.  The man page says "Do not wait for data
which is not immediately available."  Data in pmem *is* immediately
available.  If we wanted to enforce a latency threshold for submission,
it would have to be configurable and, ideally, a part of the API.  I
don't think it's something we should even try to guarantee, though,
unless application writers are asking for it.

So, I think with the change to return -EAGAIN for writes to poisoned
memory, this patch is probably ok.

Chaitanya, could you send a v2?

Thanks,
Jeff


  reply	other threads:[~2023-08-02 15:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 22:46 [PATCH V2 0/1] pmem: set QUEUE_FLAG_NOWAIT Chaitanya Kulkarni
2023-07-31 22:46 ` [PATCH V2 1/1] " Chaitanya Kulkarni
2023-08-01 15:23   ` Jeff Moyer
2023-08-01 15:59     ` Christoph Hellwig
2023-08-01 17:49       ` Jeff Moyer
2023-08-02  1:25         ` Chaitanya Kulkarni
2023-08-02 12:30           ` Christoph Hellwig
2023-08-02 15:27             ` Jeff Moyer [this message]
2023-08-03  3:24               ` Chaitanya Kulkarni
2023-08-03 13:11                 ` Jeff Moyer
2023-08-02 15:36             ` Jens Axboe
2023-08-02 16:25               ` Christoph Hellwig
2023-08-03  3:21               ` Chaitanya Kulkarni
2023-08-03  3:17             ` Chaitanya Kulkarni

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=x49o7jpv50v.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=chaitanyak@nvidia.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=hch@lst.de \
    --cc=ira.weiny@intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox