From: Christoph Hellwig <hch@infradead.org>
To: "Belanger, Martin" <Martin.Belanger@dell.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
"smith, erik" <Erik.Smith@dell.com>,
"Ghalam, Joe" <Joe.Ghalam@dell.com>,
"Hayes, Stuart" <Stuart.Hayes@dell.com>,
"White, Joseph L" <Joseph.L.White@dell.com>,
"Glimcher, Boris" <Boris.Glimcher@dell.com>
Subject: Re: nvme-fabrics: devices are uninterruptable
Date: Tue, 17 Jan 2023 02:51:54 -0800 [thread overview]
Message-ID: <Y8Z9ypvhwFYUnqkp@infradead.org> (raw)
In-Reply-To: <BLAPR19MB453154491C6DE9CB7C2A310BF2FC9@BLAPR19MB4531.namprd19.prod.outlook.com>
On Wed, Jan 11, 2023 at 02:37:58PM +0000, Belanger, Martin wrote:
> POSIX.1 specifies that certain functions such as read() or write() can act as cancellation points.
device special files are mostly out of scope for the normal Posix
rules..
> I wanted to ask the community if there is a reason for the nvme driver to not support POSIX cancellation points? I also wanted to know whether it would be possible to add support for it? Is there a downside to doing so?
How do you propose to allow for safe interruption?
next prev parent reply other threads:[~2023-01-17 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230111144340epcas5p3940d3fbf8bd19771bf1fb55ba56ecf95@epcas5p3.samsung.com>
2023-01-11 14:37 ` nvme-fabrics: devices are uninterruptable Belanger, Martin
2023-01-12 5:36 ` Kanchan Joshi
2023-01-12 10:38 ` Hannes Reinecke
2023-01-13 11:26 ` Martin Wilck
2023-01-13 16:58 ` Belanger, Martin
2023-01-17 10:51 ` Christoph Hellwig [this message]
2023-01-17 15:28 ` Belanger, Martin
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=Y8Z9ypvhwFYUnqkp@infradead.org \
--to=hch@infradead.org \
--cc=Boris.Glimcher@dell.com \
--cc=Erik.Smith@dell.com \
--cc=Joe.Ghalam@dell.com \
--cc=Joseph.L.White@dell.com \
--cc=Martin.Belanger@dell.com \
--cc=Stuart.Hayes@dell.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-nvme@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox