On Wed, 2014-08-13 at 15:14 +0300, Boaz Harrosh wrote:
> From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
>
> With current values fdisk does the wrong thing.
>
> Setting all values to 1, will make everything nice and easy.
>
> Note that current code had a BUG with anything bigger than
> 64G because hd_geometry->cylinders is ushort and it would
> overflow at this value. Any way capacity is not calculated
> through getgeo so it does not matter what you put here.
>
> Signed-off-by: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
> ---
> drivers/block/prd.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/block/prd.c b/drivers/block/prd.c
> index cc0aabf..62af81e 100644
> --- a/drivers/block/prd.c
> +++ b/drivers/block/prd.c
> @@ -55,10 +55,18 @@ struct prd_device {
>
> static int prd_getgeo(struct block_device *bd, struct hd_geometry *geo)
> {
> - /* some standard values */
> - geo->heads = 1 << 6;
> - geo->sectors = 1 << 5;
> - geo->cylinders = get_capacity(bd->bd_disk) >> 11;
> + /* Just tell fdisk to get out of the way. The math here is so
> + * convoluted and does not make any sense at all. With all 1s
> + * The math just gets out of the way.
> + * NOTE: I was trying to get some values that will make fdisk
> + * Want to align first sector on 4K (like 8, 16, 20, ... sectors) but
> + * nothing worked, I searched the net the math is not your regular
> + * simple multiplication at all. If you managed to get these please
> + * fix here. For now we use 4k physical sectors for this
> + */
> + geo->heads = 1;
> + geo->sectors = 1;
> + geo->cylinders = 1;
> return 0;
> }
I'm okay with this change, but can you let me know in which case fdisk was
previously doing the wrong thing? I'm just curious because I never saw it
misbehave, and wonder what else I should be testing.
Regarding the note in the comment, is this addressed by the
blk_queue_physical_block_size() and prd->prd_queue->limits.io_min changes in
your patch 5/9, or is it an open issue? Either way, can we nix the NOTE?
Also, you put "SQUASHME" on this patch. I'm planning on squashing all of my
patches together into an "initial version" type patch (see
https://github.com/01org/prd). Based on this, it probably makes sense to keep
it separate so you get credit for the patch?
- Ross
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
