From: Juergen Gross <jgross@suse.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xenproject.org, Ian Jackson <iwj@xenproject.org>,
Wei Liu <wl@xen.org>
Subject: Re: [PATCH v2 2/2] tools/xenstore: set open file descriptor limit for xenstored
Date: Fri, 11 Jun 2021 07:01:31 +0200 [thread overview]
Message-ID: <eaf53d99-fee9-0c79-7f29-efd00aae4d16@suse.com> (raw)
In-Reply-To: <20210608183833.023551f4.olaf@aepfle.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 432 bytes --]
On 08.06.21 18:39, Olaf Hering wrote:
> Am Tue, 8 Jun 2021 07:58:39 +0200
> schrieb Juergen Gross <jgross@suse.com>:
>
>> +#XENSTORED_MAX_N_DOMAINS=32768
>
> This will break fillup.
Why? You realize that above is a comment just documenting the default?
> Provide an empty variable like it is done for a few others in that file.
I'm following the pattern of basically all variables in that file, BTW.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2021-06-11 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 5:58 [PATCH v2 0/2] tools/xenstore: set resource limits of xenstored Juergen Gross
2021-06-08 5:58 ` [PATCH v2 1/2] tools/xenstore: set oom score for xenstore daemon on Linux Juergen Gross
2021-07-08 17:40 ` Julien Grall
2021-07-09 12:34 ` Juergen Gross
2021-07-12 8:38 ` Julien Grall
2021-06-08 5:58 ` [PATCH v2 2/2] tools/xenstore: set open file descriptor limit for xenstored Juergen Gross
2021-06-08 16:39 ` Olaf Hering
2021-06-11 5:01 ` Juergen Gross [this message]
2021-06-11 5:46 ` Olaf Hering
2021-06-11 7:07 ` Juergen Gross
2021-06-11 7:28 ` Olaf Hering
2021-07-07 7:23 ` [PATCH v2 0/2] tools/xenstore: set resource limits of xenstored Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eaf53d99-fee9-0c79-7f29-efd00aae4d16@suse.com \
--to=jgross@suse.com \
--cc=iwj@xenproject.org \
--cc=olaf@aepfle.de \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.