* Why the field 'depth use different data types in sbitmap and sbitmap_word
@ 2017-01-07 13:21 Wang Sheng-Hui
2017-01-08 23:08 ` Jens Axboe
0 siblings, 1 reply; 3+ messages in thread
From: Wang Sheng-Hui @ 2017-01-07 13:21 UTC (permalink / raw)
To: Jens Axboe, linux-block
Hi,
Sorry to trouble you.
I have one question about the define of struct sbitmap & sbitmap_word:
In sbitmap_word, the field depth is 'unsigned long', but in sbitmap, the field depth is 'unsigned int'.
Why they use different data types?
Regards,
shenghui
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Why the field 'depth use different data types in sbitmap and sbitmap_word
2017-01-07 13:21 Why the field 'depth use different data types in sbitmap and sbitmap_word Wang Sheng-Hui
@ 2017-01-08 23:08 ` Jens Axboe
2017-01-09 2:43 ` Wang Sheng-Hui
0 siblings, 1 reply; 3+ messages in thread
From: Jens Axboe @ 2017-01-08 23:08 UTC (permalink / raw)
To: Wang Sheng-Hui, linux-block
On 01/07/2017 06:21 AM, Wang Sheng-Hui wrote:
> Hi,
>
> Sorry to trouble you.
>
> I have one question about the define of struct sbitmap & sbitmap_word:
> In sbitmap_word, the field depth is 'unsigned long', but in sbitmap, the field depth is 'unsigned int'.
> Why they use different data types?
No particular reason. The bit ops use unsigned long, so that is why
sbitmap_word uses it. unsigned int should be enough for sbitmap in
general.
--
Jens Axboe
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Why the field 'depth use different data types in sbitmap and sbitmap_word
2017-01-08 23:08 ` Jens Axboe
@ 2017-01-09 2:43 ` Wang Sheng-Hui
0 siblings, 0 replies; 3+ messages in thread
From: Wang Sheng-Hui @ 2017-01-09 2:43 UTC (permalink / raw)
To: Jens Axboe, linux-block
On 1/9/2017 7:08 AM, Jens Axboe wrote:
> On 01/07/2017 06:21 AM, Wang Sheng-Hui wrote:
>> Hi,
>>
>> Sorry to trouble you.
>>
>> I have one question about the define of struct sbitmap & sbitmap_word:
>> In sbitmap_word, the field depth is 'unsigned long', but in sbitmap, the field depth is 'unsigned int'.
>> Why they use different data types?
> No particular reason. The bit ops use unsigned long, so that is why
> sbitmap_word uses it. unsigned int should be enough for sbitmap in
> general.
>
Got it, Jens.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-01-09 2:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-07 13:21 Why the field 'depth use different data types in sbitmap and sbitmap_word Wang Sheng-Hui
2017-01-08 23:08 ` Jens Axboe
2017-01-09 2:43 ` Wang Sheng-Hui
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.