Neal Pollack wrote:
> On 12/ 2/09 08:40 AM, Joerg Schilling wrote:
>> "Garrett D'Amore" <gdamore at Sun.COM> wrote:
>>
>>
>>> Okay, I'm going to propose solving this properly. The solution is that
>>> the following structure:
>>>
>>> struct bd_media {
>>> uint64_t m_nblks;
>>> boolean_t m_readonly;
>>> };
>>>
>>> Will grow a new member expressing the block size:
>>>
>>> struct bd_media {
>>> uint64_t m_nblks;
>>> uint32_t m_blksize;
>>> boolean_t m_readonly;
>>> };
>>>
>>
>> the structure content looks OK, but I and many other people
>> will read "bd_media" as BluRay-Disk Media.....
>>
>
> agreed. bd_anything is commonly understood in the industry
> to apply to bluray.
>
> I am not a voting member, but give the case a silent +1 if
> the structure name can be anything else :-)
The structure isn't used anywhere where I believe this confusion is
likely to be an issue.
Specifically, it is only exchanged between the "blkdev" framework, and
blkdev adapter drivers. Neither of these have anything to do with bluray.
- Garrett
