From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: pupilla@hotmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: ipsec: ipcomp - Decompress into frags if necessary
Date: Fri, 25 Jul 2008 02:58:01 -0700 (PDT) [thread overview]
Message-ID: <20080725.025801.229691344.davem@davemloft.net> (raw)
In-Reply-To: <20080725074328.GB16747@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Fri, 25 Jul 2008 15:43:28 +0800
> On Fri, Jul 25, 2008 at 03:41:09PM +0800, Herbert Xu wrote:
> >
> > Here is the first part:
>
> And finally:
>
> ipsec: ipcomp - Decompress into frags if necessary
>
> When decompressing extremely large packets allocating them through
> kmalloc is prone to failure. Therefore it's better to use page
> frags instead.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Also applied, nice work Herbert.
About MAX_SKB_FRAGS, if we go over that limit we probably need to
log a message or something because we'll likely get that same kind
of huge sized packet that we can't handle in future retransmits.
There is no way to figure out that this is what is happening.
Actually I wonder if it's even possible. Our limit is 64K anyways
(and that's our scratch buffer size) and MAX_SKB_FRAGS is always
large enough to accomodate at least 64K of data.
So perhaps it wants a WARN_ON :-)
next prev parent reply other threads:[~2008-07-25 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 6:39 2.6.26: [<c0133cc1>] __alloc_pages_internal+0x331/0x343 Marco Berizzi
2008-07-24 6:45 ` David Miller
2008-07-24 13:06 ` Herbert Xu
2008-07-25 7:41 ` Herbert Xu
2008-07-25 7:43 ` ipsec: ipcomp - Decompress into frags if necessary Herbert Xu
2008-07-25 9:58 ` David Miller [this message]
2008-07-25 10:46 ` Herbert Xu
2008-07-25 10:55 ` David Miller
2008-07-25 9:54 ` 2.6.26: [<c0133cc1>] __alloc_pages_internal+0x331/0x343 David Miller
2008-07-24 15:06 ` Marco Berizzi
2008-07-25 14:18 ` Herbert Xu
2008-07-25 14:19 ` Herbert Xu
2008-07-25 19:19 ` Marco Berizzi
2008-07-25 20:12 ` David Miller
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=20080725.025801.229691344.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pupilla@hotmail.com \
/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
all inboxes | Powered by JetHome®