On Wed, May 17, 2017 at 06:07:42PM +0300, Nikolay Borisov wrote:
> Currently the struct space_info creation code is intermixed in the
> udpate_space_info function. There are well-defined points at which the we
> actually want to create brand-new space_info structs (e.g. during mount of
> the
On Wed, May 17, 2017 at 4:55 PM, Jeff Mahoney wrote:
> On 5/17/17 4:52 PM, Noah Massey wrote:
>> On Wed, May 17, 2017 at 4:34 PM, Nikolay Borisov wrote:
>>>
>>>
>>> On 17.05.2017 21:57, Noah Massey wrote:
On Wed, May 17, 2017 at 11:07 AM, Nikolay Borisov
On 5/17/17 4:52 PM, Noah Massey wrote:
> On Wed, May 17, 2017 at 4:34 PM, Nikolay Borisov wrote:
>>
>>
>> On 17.05.2017 21:57, Noah Massey wrote:
>>> On Wed, May 17, 2017 at 11:07 AM, Nikolay Borisov wrote:
Currently the struct space_info creation code
On Wed, May 17, 2017 at 4:34 PM, Nikolay Borisov wrote:
>
>
> On 17.05.2017 21:57, Noah Massey wrote:
>> On Wed, May 17, 2017 at 11:07 AM, Nikolay Borisov wrote:
>>> Currently the struct space_info creation code is intermixed in the
>>> udpate_space_info
On 17.05.2017 21:57, Noah Massey wrote:
> On Wed, May 17, 2017 at 11:07 AM, Nikolay Borisov wrote:
>> Currently the struct space_info creation code is intermixed in the
>> udpate_space_info function. There are well-defined points at which the we
>
> ^^^ update_space_info
>
On Wed, May 17, 2017 at 11:07 AM, Nikolay Borisov wrote:
> Currently the struct space_info creation code is intermixed in the
> udpate_space_info function. There are well-defined points at which the we
^^^ update_space_info
> actually want to create brand-new space_info
Currently the struct space_info creation code is intermixed in the
udpate_space_info function. There are well-defined points at which the we
actually want to create brand-new space_info structs (e.g. during mount of
the filesystem as well as sometimes when adding/initialising new chunks). In
such