From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org,
martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org,
linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints
Date: Mon, 26 Jun 2017 07:55:27 -0600 [thread overview]
Message-ID: <91b3fd3b-18f5-cf8c-a1d7-c0637283ce14@kernel.dk> (raw)
In-Reply-To: <20170626095148.GB14057-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On 06/26/2017 03:51 AM, Christoph Hellwig wrote:
> Please document the userspace API (added linux-api and linux-man
> to CC for sugestions), especially including the odd effects of the
> per-inode settings.
Of course, I'll send in a diff for the fcntl(2) man page.
> Also I would highly recommend to use different fcntl commands
> for the file vs inode hints to avoid any strange behavior.
OK, used to have that too... I can add specific _FILE versions.
--
Jens Axboe
next prev parent reply other threads:[~2017-06-26 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1498004526-4543-1-git-send-email-axboe@kernel.dk>
[not found] ` <1498004526-4543-2-git-send-email-axboe@kernel.dk>
[not found] ` <1498004526-4543-2-git-send-email-axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-06-26 9:51 ` [PATCH 1/9] fs: add fcntl() interface for setting/getting write life time hints Christoph Hellwig
[not found] ` <20170626095148.GB14057-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-06-26 13:55 ` Jens Axboe [this message]
[not found] ` <91b3fd3b-18f5-cf8c-a1d7-c0637283ce14-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
2017-06-26 16:09 ` Darrick J. Wong
[not found] ` <20170626160946.GI3787-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2017-06-26 16:29 ` Jens Axboe
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=91b3fd3b-18f5-cf8c-a1d7-c0637283ce14@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).