From: David Miller <davem@davemloft.net>
To: besser82@fedoraproject.org
Cc: waltje@uWalt.NL.Mugnet.ORG, flla@stud.uni-sb.de,
A.Cox@swansea.ac.uk, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, trivial@kernel.org, labbott@redhat.com,
zbyszek@in.waw.pl
Subject: Re: [PATCH 4.15-rc8] net/core: Increase default optmem_max limit
Date: Tue, 16 Jan 2018 09:30:56 -0500 (EST) [thread overview]
Message-ID: <20180116.093056.695073638764843370.davem@davemloft.net> (raw)
In-Reply-To: <e7459a93ac46bfe902a1f5b9fd57ed3488feb465.camel@fedoraproject.org>
From: Björn 'besser82' Esser <besser82@fedoraproject.org>
Date: Tue, 16 Jan 2018 00:59:11 +0100
> @@ -316,7 +316,7 @@ __u32 sysctl_wmem_default __read_mostly
> __u32 sysctl_rmem_default __read_mostly = SK_RMEM_MAX;
>
> /* Maximal
> space eaten by iovec or ancillary data plus some space */
This patch is corrupted by your email client, it has chopped up long
lines and turned TABs into a series of SPACE characters.
> -int sysctl_optmem_max __read_mostly = sizeof(unsigned long)*(2*UIO_MAXIOV+512);
> +int
> sysctl_optmem_max __read_mostly = sizeof(unsigned long)*4*(2*UIO_MAXIOV+512);
> EXPORT_SYMBOL(sysctl_optmem_max);
Please style this in a more appropriate manner.
Thank you.
next prev parent reply other threads:[~2018-01-16 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 23:59 [PATCH 4.15-rc8] net/core: Increase default optmem_max limit Björn 'besser82' Esser
2018-01-16 0:16 ` Björn 'besser82' Esser
2018-01-16 14:30 ` David Miller [this message]
2018-01-16 17:13 ` [PATCH v2] " Björn 'besser82' Esser
2018-01-16 17:16 ` Björn 'besser82' Esser
2018-01-16 18:11 ` Stephan Mueller
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 0:04 [PATCH 4.15-rc8] " Björn 'besser82' Esser
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=20180116.093056.695073638764843370.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=A.Cox@swansea.ac.uk \
--cc=besser82@fedoraproject.org \
--cc=flla@stud.uni-sb.de \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=waltje@uWalt.NL.Mugnet.ORG \
--cc=zbyszek@in.waw.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).