fix bugs related to introduction of flag --blocksize_kb

[emillynge]

Dear maintainers

Please accept this PR which fixes a couple of issues that has arisen due to the introduction of --blocksize_kb option.

In general these issue stem from the previous assumption that a block is 1MB.

The stats MBps and MB are wrong when bz!=1MB
Files are not rotated at the right time. Specifically, bz>1MB can lead to a PKT file larger than 4Gb which causes a fatal error.
To fix the issue, i've introduced a new variable blocks_per_file which is determined by the values flag_filesize_mband flag_blocksize_kb.

I'm not entirely sure whether the pattern of calculating blocks_per_file in the switch block is the right way to go.

NB: closed previous PR in order to create PR from company repo instead

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[emillynge]

@googlebot I signed it!

[wehowsky-admin]

@googlebot I signed it!

[emillynge]

@googlebot I signed it!

[emillynge]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[gconnell]

Thanks, and sorry for the late reply!