From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, linux-block <linux-block@vger.kernel.org>,
Alasdair G Kergon <agk@redhat.com>,
AliOS system security <alios_sys_security@linux.alibaba.com>,
Colin Ian King <colin.king@canonical.com>,
Eric Biggers <ebiggers@google.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Milan Broz <gmazyland@gmail.com>,
Nikos Tsironis <ntsironis@arrikto.com>,
Shenghui Wang <shhuiw@foxmail.com>,
Sweet Tea <sweettea@redhat.com>,
wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>
Subject: Re: [git pull] device mapper changes for 4.21
Date: Wed, 2 Jan 2019 23:27:54 -0800 [thread overview]
Message-ID: <20190103072754.GA2667@infradead.org> (raw)
In-Reply-To: <CAHk-=wh89gmqGaK4K7+ns9S6CSeCfuUmiy8GPeVz8_ntMz-DYg@mail.gmail.com>
On Sun, Dec 30, 2018 at 04:25:46PM -0800, Linus Torvalds wrote:
> On Sun, Dec 30, 2018 at 11:15 AM Mikulas Patocka <mpatocka@redhat.com> wrote:
> >
> > But you're right that 2TiB devices are common and that perhaps this option
> > should go away.
>
> 2TiB devices are definitely not common in the one situation where this
> option might matter: small embedded devices.
>
> I don't think the cost of 64 bit is in the arithmetic, but it might be
> in some of the data structures.
>
> But my gut feel is that it probably doesn't much matter, and we could
> get rid of the config option without anybody ever noticing. I don't
> think we have that many data structures with 'sector_t' in them.
>
> We might try to first just force the option on, and see if anybody even cares.
Our smallest embedded devices use raw flash using the MTD subsystem,
and even that is using 64-bit size types everywhere. So I'd be really
surprised if it is an issue.
>
> Linus
---end quoted text---
next prev parent reply other threads:[~2019-01-03 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 16:09 [git pull] device mapper changes for 4.21 Mike Snitzer
2018-12-29 1:30 ` pr-tracker-bot
2018-12-30 9:06 ` Christoph Hellwig
2018-12-30 19:15 ` Mikulas Patocka
2018-12-31 0:25 ` Linus Torvalds
2019-01-03 7:27 ` Christoph Hellwig [this message]
2019-01-03 7:45 ` Milan Broz
2018-12-30 19:40 ` James Bottomley
2018-12-31 20:10 ` 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=20190103072754.GA2667@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=alios_sys_security@linux.alibaba.com \
--cc=colin.king@canonical.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=gmazyland@gmail.com \
--cc=heinzm@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ntsironis@arrikto.com \
--cc=shhuiw@foxmail.com \
--cc=snitzer@redhat.com \
--cc=sweettea@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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).