From: Brice Goglin <brice.goglin@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Why is SECTOR_SIZE = 512 inside kernel ?
Date: Tue, 18 Aug 2015 23:06:47 +0200 [thread overview]
Message-ID: <55D39E67.3010009@gmail.com> (raw)
In-Reply-To: <20150817135450.GB27202@thunk.org>
Le 17/08/2015 15:54, Theodore Ts'o a écrit :
>
> It's cast in stone. There are too many places all over the kernel,
> especially in a huge number of file systems, which assume that the
> sector size is 512 bytes. So above the block layer, the sector size
> is always going to be 512.
Could this be a problem when using pmem/nvdimm devices with
byte-granularity (no BTT layer)? (hw_sector_size reports
512 in this case while we could expect 1 instead).
Or it just doesn't matter because BTT is the only way to use
these devices for filesystems like other block devices?
thanks
Brice
next prev parent reply other threads:[~2015-08-18 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 12:53 Why is SECTOR_SIZE = 512 inside kernel ? Navin P
2015-08-17 13:54 ` Theodore Ts'o
2015-08-18 21:06 ` Brice Goglin [this message]
2015-08-18 21:38 ` tytso
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=55D39E67.3010009@gmail.com \
--to=brice.goglin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).