On 2013年01月04日 22:30, Eric Blake wrote:
On 01/03/2013 08:35 PM, Osier Yang wrote:
...when you could just use a single int value comprising the combination
of major and minor as the hash key, if only you had used
Sounds good, how about something like "805516", where "8" is major, and
"16" is t
On 01/03/2013 08:35 PM, Osier Yang wrote:
>> ...when you could just use a single int value comprising the combination
>> of major and minor as the hash key, if only you had used
>
> Sounds good, how about something like "805516", where "8" is major, and
> "16" is the minor? It should be small eno
On 2013年01月04日 04:02, Eric Blake wrote:
On 01/02/2013 07:37 AM, Osier Yang wrote:
This introduces a hash table for qemu driver, to store the shared
disk's info as (@major:minor, @ref_count). @ref_count is the number
of domains which shares the disk.
Since we only care about if the disk support
On 01/02/2013 07:37 AM, Osier Yang wrote:
> This introduces a hash table for qemu driver, to store the shared
> disk's info as (@major:minor, @ref_count). @ref_count is the number
> of domains which shares the disk.
>
> Since we only care about if the disk support unprivileged SG_IO
> commands, an
This introduces a hash table for qemu driver, to store the shared
disk's info as (@major:minor, @ref_count). @ref_count is the number
of domains which shares the disk.
Since we only care about if the disk support unprivileged SG_IO
commands, and the SG_IO commands only make sense for block disk,
t
This introduces a hash table for qemu driver, to store the shared
disk's info as (@major:minor, @ref_count). @ref_count is the number
of domains which shares the disk.
Since we only care about if the disk support unprivileged SG_IO
commands, and the SG_IO commands only make sense for block disk,
t
