From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH] inet: fix enforcing of fragment queue hash list depth
Date: Mon, 15 Apr 2013 19:16:26 +0200 [thread overview]
Message-ID: <1366046186.11284.70.camel@localhost> (raw)
In-Reply-To: <20130415152637.GA29378@order.stressinduktion.org>
On Mon, 2013-04-15 at 17:26 +0200, Hannes Frederic Sowa wrote:
> I will have to play with this patch a bit. Perhaps I have some more insights
> after that. :)
I would actually like to do/finish up this patch my self, as I have
several patches in this code area. But I would value your input :-)
--Jesper
next prev parent reply other threads:[~2013-04-15 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 14:25 [RFC PATCH] inet: fix enforcing of fragment queue hash list depth Jesper Dangaard Brouer
2013-04-15 15:26 ` Hannes Frederic Sowa
2013-04-15 16:23 ` Eric Dumazet
2013-04-15 17:09 ` Hannes Frederic Sowa
2013-04-15 17:12 ` Jesper Dangaard Brouer
2013-04-15 17:16 ` Jesper Dangaard Brouer [this message]
2013-04-15 17:43 ` Hannes Frederic Sowa
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=1366046186.11284.70.camel@localhost \
--to=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.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.