diff options
author | Boaz Harrosh <boaz@plexistor.com> | 2015-01-07 18:09:38 +0200 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2015-01-13 21:59:15 -0700 |
commit | c8fa31730fc72a83bad762112a872675b3e76886 (patch) | |
tree | 4ca498cb2c8e7899d13e29448fa105fcd6a23d45 /tools/perf/scripts/python/event_analyzing_sample.py | |
parent | 937af5ecd0591e84ee54180fa97dcbe9bbe5fed6 (diff) |
brd: Request from fdisk 4k alignment
Because of the direct_access() API which returns a PFN. partitions
better start on 4K boundary, else offset ZERO of a partition will
not be aligned and blk_direct_access() will fail the call.
By setting blk_queue_physical_block_size(PAGE_SIZE) we can communicate
this to fdisk and friends.
The call to blk_queue_physical_block_size() is harmless and will
not affect the Kernel behavior in any way. It is only for
communication to user-mode.
before this patch running fdisk on a default size brd of 4M
the first sector offered is 34 (BAD), but after this patch it
will be 40, ie 8 sectors aligned. Also when entering some random
partition sizes the next partition-start sector is offered 8 sectors
aligned after this patch. (Please note that with fdisk the user
can still enter bad values, only the offered default values will
be correct)
Note that with bdev-size > 4M fdisk will try to align on a 1M
boundary (above first-sector will be 2048), in any case.
CC: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Boaz Harrosh <boaz@plexistor.com>
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions