From: Jens Axboe <axboe@kernel.dk>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>, Jon Tango <cheerios123@outlook.com>
Subject: Re: linux /dev and normal files
Date: Fri, 03 Apr 2015 12:24:23 -0600 [thread overview]
Message-ID: <551EDAD7.3050803@kernel.dk> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B40295A858295@G9W0745.americas.hpqcorp.net>
On 04/03/2015 12:13 PM, Elliott, Robert (Server Storage) wrote:
>
>
>> -----Original Message-----
>> From: fio-owner@vger.kernel.org [mailto:fio-owner@vger.kernel.org] On
>> Behalf Of Jens Axboe
>> Sent: Thursday, October 2, 2014 1:32 PM
>> To: Elliott, Robert (Server Storage); fio@vger.kernel.org
>> Cc: Sitsofe Wheeler; Jon Tango
>> Subject: Re: linux /dev and normal files
>>
>> On 10/02/2014 12:21 PM, Elliott, Robert (Server Storage) wrote:
>>>>>> It might be better to continue to attempt to run the
>>>>>> other jobs.
>>>>>
>>>>> We should just go for the simpler create/nocreate solution, I prefer
>>>>> that. This is too involved, and it's hard to get all the cases right
>>>>> since there are a bunch of different ways that files are added. Which
>>>>> was why this patch only focused on filename=, since that is the one
>> that
>>>>> is the most interesting. But it still isn't pretty. If we add the
>>>>> allow_file_create option, it's basically a two-liner change in a few
>>>>> places to not use O_CREAT.
>>>>
>>>> That took roughly 4 minutes... Does this work? Set allow_file_create=0
>>>> to disallow creating new files.
> ...
>>
>> OK, let me test that, will spin a new one.
>
> I don't think this ever got added.
It didn't... Did you re-test? No reason we can't get it added, I'll look
into it start next week.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-03 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 23:49 linux /dev and normal files Elliott, Robert (Server Storage)
2014-10-01 1:02 ` Jens Axboe
2014-10-01 1:12 ` Elliott, Robert (Server Storage)
2014-10-01 1:17 ` Jens Axboe
2014-10-01 3:43 ` Jens Axboe
2014-10-01 7:36 ` Sitsofe Wheeler
2014-10-01 14:20 ` Jens Axboe
2014-10-01 14:31 ` Elliott, Robert (Server Storage)
2014-10-01 23:52 ` Elliott, Robert (Server Storage)
2014-10-02 0:58 ` Jens Axboe
2014-10-02 1:03 ` Jens Axboe
2014-10-02 18:21 ` Elliott, Robert (Server Storage)
2014-10-02 18:32 ` Jens Axboe
2014-10-02 18:41 ` Jens Axboe
2015-04-03 18:13 ` Elliott, Robert (Server Storage)
2015-04-03 18:24 ` Jens Axboe [this message]
2015-05-12 15:32 ` Jens Axboe
2015-05-12 16:34 ` Elliott, Robert (Server Storage)
2015-05-12 17:56 ` 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=551EDAD7.3050803@kernel.dk \
--to=axboe@kernel.dk \
--cc=Elliott@hp.com \
--cc=cheerios123@outlook.com \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.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