From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, dalecki@evision-ventures.com
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] size-in-bytes
Date: Sat, 16 Feb 2002 21:41:21 GMT [thread overview]
Message-ID: <UTC200202162141.VAA31781.aeb@cwi.nl> (raw)
From dalecki@evision-ventures.com Sat Feb 16 22:09:26 2002
Andries.Brouwer@cwi.nl wrote:
> /*
>+ * blk_size_in_bytes contains the size of all block-devices in bytes
>+ * (blk_size has too low a resolution, since we really need the size
>+ * in 512 byte sectors, and fails on devices > 2 TB)
>+ *
>+ * blk_size_in_bytes[MAJOR][MINOR]
>+ *
>+ * if (!blk_size_in_bytes[MAJOR]) then no minor size checking is done.
>+ */
>+loff_t * blk_size_in_bytes[MAX_BLKDEV];
>+
>+/*
Please pin it up the block device structure not to just another
arbitrary global array.
You miss the point of the patch, perhaps forgot to read the introduction :-)
The point of the patch is that all applied occurrences of blk_size[][]
have disappeared. All places in the code where a size is needed, that size
comes from blkdev_size_in_bytes(), and the size comes in bytes, and the size
is a loff_t.
You want to remove these arrays - fine, so do I.
(And of course I removed them a few times, but that is another story.)
But that is an independent action. Whatever one planned to do with
blk_size[][] now applies to blk_size_in_bytes[][].
So, this patch is a step ahead but does not solve all the worlds problems
at once.
Andries
next reply other threads:[~2002-02-16 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 21:41 Andries.Brouwer [this message]
2002-02-16 22:05 ` [PATCH] size-in-bytes Martin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 9:54 Andries.Brouwer
2002-02-18 23:29 Andries.Brouwer
2002-02-18 23:38 ` Daniel Phillips
2002-02-16 22:45 Andries.Brouwer
2002-02-16 23:10 ` Martin Dalecki
2002-02-16 16:09 Andries.Brouwer
2002-02-16 21:09 ` Martin Dalecki
2002-02-18 22:43 ` Daniel Phillips
2002-02-21 7:04 ` Benjamin LaHaise
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=UTC200202162141.VAA31781.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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