[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 09/13] xen/arm: Reduce struct membank size on static shared memory
- To: Michal Orzel <michal.orzel@xxxxxxx>
- From: Luca Fancellu <Luca.Fancellu@xxxxxxx>
- Date: Wed, 10 Apr 2024 11:19:32 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6A/1qkUxhlab+P/th8YJkLqmToP6x19+FT/yJN+nPJM=; b=dgT2YBJI9nL0gBlWDjZp6Kw/ZvMKr5RikMBTk32CuBZokI4TI4YtaXK+ZpExt+sHftbFdPNPKuhLk+uKv+dr5MgVntaciMIiOE+1ZqWQWP8GN8Ik9826nYSfdiMYd7EYJuR3mp4rpcpyUMKU1eK5X5zf3lWjyrIlKlA1et0ot5N6zBff4G5P60XFa6ONrsxQhwBDEeYlI9M8KLzGyxcv2Vu8jryRc6Z1JTrBrNbyiNRGDNcb4SY0RwFBtzrpG5xWmjeeZwjPRRn4lr8gv+rIAeb8mUznRICGgzWBM33zxbj1UHkzb50URIh9nX+m15nXzU1PtBfN4ey5EN+xssVjiw==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6A/1qkUxhlab+P/th8YJkLqmToP6x19+FT/yJN+nPJM=; b=aRhlSxgPvRPP69K6k5u+xrLeLTvoMd+Y+Kr5PhKBGDjsBQSUwMvcpP299F1dbJCBuoXKtAs5MK8jQuqI056phl+EsGp3gZ12rHE1fwon6LTbbouzBFjqeL6pw443XUiIKDCC+LPODhwnFMZslNTBoZcH3drx2PUP9MJbHNFubpIR4BRddPHrB2cp1H3MVF1pLp2b+qro4sC67buFqRSrL+QKik2S3zT21OQKoeDsvC04twRfP2dWkN7WRBf3HaWxQMIvqT9J08CB6bqP9WSqyPfZMg/9L6PZBymBkEbP8GsQvhl55gT0VA5jqcuZ6d53AKR0h19rk+XnldvPqTLC0g==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=il8aPoEMIc9faAOAiVDZWjScbhJoogapYk1EhoKEkvQm3b7wKapAI2Jg7YlIxeyyFd4e+RGg619ASwpbZ9o4dWr9+rQBjGcuhM0lVrctrYWl9DtqLHQeTAlzXrHgxs8Mp6qmjiIDrKEqtpnNV5OpBC3lH9gR/MQO7e9lmhSCe7Ka0JjjpjqcUKXSB/VmzcQ7emLRASqJe+lcF5WppwDtQmifXt4VQSbKRKrZQHmmgzZ/JYI8v4VXEk55HnwtCbi00ti50GkFgVgzuFqsY3ooPOegVKBa0/50NKMVIrIx8qJ9buyNR2267tsLlrwoxMusbZux70G0+SGKxP/hG2bJ2Q==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Si7YP/iyiacaILDc9cdMOiPBezhcCRk/IOGclLNFH4gmXEVf3egnHzu8JbKm3UfaLoXwP5iOVbv0oY91ppfQ8ZKJLi5qrI6DOLgWEqgsVXr+opQuwLRSeTLs3C+OQHwILzFbQAQA8UQWIyxDJxPuObetR8EWIgYteIw5/jdMUNl9FWh91AVglat188DRknK4dLm96bu9XT5UzMLb5tCnljt1EHPpxIqKl+G9s/htHWoLt8Z3OsbgTG5EwZWxzByFuO0cEwvbBaMXDFECBcJ597SMP87R7NEzG+jr0+pA1gs3N893k563PPkjmo4jLI6VNQ0IaD0ny/JHiSsGE/BHYg==
- Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>
- Delivery-date: Wed, 10 Apr 2024 11:19:57 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Thread-index: AQHainOQqOQ8ACmqS0SD80lqrmS1tLFhR1gAgAAPMQCAAAF2AIAABPiA
- Thread-topic: [PATCH v2 09/13] xen/arm: Reduce struct membank size on static shared memory
>>>>
>>>> Afterwards, create a new structure 'struct shared_meminfo' which
>>>> has the same interface of 'struct meminfo', but requires less
>>> I would expect some justification for selecting 32 as the max number of
>>> shmem banks
>>
>> So I have to say I picked up a value I thought was ok for the amount of
>> shared memory
>> Banks, do you think it is too low? The real intention here was to decouple
>> the number
>> of shared memory banks from the number of generic memory banks, and I felt
>> 32 was enough,
>> but if you think it might be an issue I could bump it, or we could have a
>> Kconfig...
> No need for Kconfig. 32 is enough for now but I expect a paragraph in commit
> msg that you select
> 32 which should be enough for current use cases and can be bumped in the
> future in case there is a need.
What do you think of this proposal:
[...]
hence the 'struct membank' won't grow in size.
Afterwards, create a new structure 'struct shared_meminfo' which
has the same interface of 'struct meminfo', but requires less
banks, defined by the number in NR_SHMEM_BANKS, which is 32 at the
moment and should be enough for the current use cases, the value
might be increased in te future if needed.
Finally, this structure hosts also the extra information for the
static shared memory banks.
The fields 'bank' and 'extra' of this structure are meant to be
[...]
Cheers,
Luca
|