[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] blkback feature announcement

>>> On 08.12.15 at 02:08, <bob.liu@xxxxxxxxxx> wrote:
> On 12/07/2015 08:42 PM, Roger Pau Monnà wrote:
>> El 07/12/15 a les 13.00, Jan Beulich ha escrit:
>>> Hello,
>>> is there a particular reason why "max-ring-page-order" gets written in
>>> xen_blkbk_probe(), but e.g. "feature-max-indirect-segments" and
>>> "feature-persistent" get written only in connect(), despite both having
>>> constant values (and hence the node value effectively being known as
>>> soon as the device exists)?
>> No, AFAIK there's no specific reason.
> AFAIR, that's for the blkfront resume path.
> We need to get the "max-ring-page-order" in blkfront_resume() in advance, so 
> that we can know how many ring pages to be used before setup_blkring().

I don't follow - the proposal is to have the backend announce the
feature _earlier_, so how could frontend resume be affected?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.