From: Linda Knippers <linda.knippers@hp.com>
To: Jeff Moyer <jmoyer@redhat.com>, Boaz Harrosh <boaz@plexistor.com>
Cc: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: regression introduced by "block: Add support for DAX reads/writes to block devices"
Date: Thu, 13 Aug 2015 12:42:32 -0400 [thread overview]
Message-ID: <55CCC8F8.6080204@hp.com> (raw)
In-Reply-To: <x49fv3n5lw9.fsf@segfault.boston.devel.redhat.com>
On 8/13/2015 10:00 AM, Jeff Moyer wrote:
> Boaz Harrosh <boaz@plexistor.com> writes:
>
>> On 08/13/2015 12:11 AM, Jeff Moyer wrote:
>>> Boaz Harrosh <boaz@plexistor.com> writes:
>>>
>>>> On 08/07/2015 11:41 PM, Jeff Moyer wrote:
>>>> <>
>>>>>
>>>>>> We need to cope with the case where the end of a partition isn't on a
>>>>>> page boundary though.
>>>>>
>>>>> Well, that's usually done by falling back to buffered I/O. I gave that
>>>>> a try and panicked the box. :) I'll keep looking into it, but probably
>>>>> won't have another patch until next week.
>>>>>
>>>>
>>>> lets slow down for a sec, please.
>>>>
>>>> We have all established that an unaligned partition start is BAD and not supported?
>>>
>>> No. Unaligned partitions on RAID arrays or 512e devices are bad because
>>> they result in suboptimal performance. They are most certainly still
>>> supported, though.
>>>
>>
>> What ?
>>
>> I meant for dax on pmem or brd. I meant that we *do not* support dax access
>> on an unaligned partition start. (None dax is perfectly supported)
>
> Sorry, I thought your statement was broader than that.
>
>> We did it this way because of the direct_access API that returns a pfn
>> with is PAGE_SIZE. We could introduce a pfn+offset but we thought it is
>> not worth it, and that dax should be page aligned for code simplicity
>
> I'd be fine with changing the persistent memory block device to only
> support 4k logical, 4k physical block size. That probably makes the
> most sense.
If that's what we want, the current patch doesn't do that.
https://lists.01.org/pipermail/linux-nvdimm/2015-July/001555.html
It causes the physical block size to be PAGE_SIZE but the
logical block size is still 512. However, the minimum_io_size
is now 4096 (same as physical block size, I assume). The
optimal_io_size is still 0. What does that mean?
Whatever we go with, we should do something because 4.2rc6 is still
broken, unable to create a xfs file system on a pmem device, ever
since the change to use DAX on block devices with O_DIRECT.
-- ljk
>
> Cheers,
> Jeff
>
next prev parent reply other threads:[~2015-08-13 16:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 20:19 regression introduced by "block: Add support for DAX reads/writes to block devices" Jeff Moyer
2015-08-05 22:01 ` Dave Chinner
2015-08-06 1:42 ` Linda Knippers
2015-08-06 3:24 ` Dave Chinner
2015-08-06 7:52 ` Boaz Harrosh
2015-08-06 20:34 ` Dave Chinner
2015-08-09 8:52 ` Boaz Harrosh
2015-08-10 16:32 ` Linda Knippers
2015-08-10 21:27 ` Dave Chinner
2015-08-10 23:04 ` Linda Knippers
2015-08-06 14:21 ` Wilcox, Matthew R
2015-08-06 15:33 ` Jeff Moyer
2015-08-06 15:51 ` Wilcox, Matthew R
2015-08-06 21:30 ` Jeff Moyer
2015-08-07 18:11 ` Wilcox, Matthew R
2015-08-07 20:41 ` Jeff Moyer
2015-08-10 7:42 ` Boaz Harrosh
2015-08-12 21:11 ` Jeff Moyer
2015-08-13 5:32 ` Boaz Harrosh
2015-08-13 14:00 ` Jeff Moyer
2015-08-13 16:42 ` Linda Knippers [this message]
2015-08-13 17:14 ` Jeff Moyer
2015-08-13 17:52 ` Linda Knippers
2015-08-13 18:19 ` Jeff Moyer
2015-08-13 19:32 ` Wilcox, Matthew R
2015-08-14 16:28 ` 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=55CCC8F8.6080204@hp.com \
--to=linda.knippers@hp.com \
--cc=boaz@plexistor.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.r.wilcox@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 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.