From: David Miller <davem@davemloft.net>
To: rshriram@cs.ubc.ca
Cc: hadi@cyberus.ca, netdev@vger.kernel.org, brendan@cs.ubc.ca
Subject: Re: [PATCH] net/sched: sch_plug - Queue traffic until an explicit release command
Date: Mon, 19 Dec 2011 16:35:17 -0500 (EST) [thread overview]
Message-ID: <20111219.163517.142436937064950002.davem@davemloft.net> (raw)
In-Reply-To: <1324329752-28459-1-git-send-email-rshriram@cs.ubc.ca>
From: rshriram@cs.ubc.ca
Date: Mon, 19 Dec 2011 13:22:32 -0800
> +#define FIFO_BUF (10*1024*1024)
This limit is, at best, extremely arbitrary.
next prev parent reply other threads:[~2011-12-19 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 21:22 [PATCH] net/sched: sch_plug - Queue traffic until an explicit release command rshriram
2011-12-19 21:27 ` Shriram Rajagopalan
2011-12-19 21:53 ` David Miller
2011-12-19 21:32 ` Stephen Hemminger
2011-12-19 21:35 ` David Miller [this message]
2011-12-20 14:38 ` Jamal Hadi Salim
2011-12-20 17:05 ` Shriram Rajagopalan
2011-12-21 14:54 ` Jamal Hadi Salim
[not found] ` <CAP8mzPNtei=6oVC8APf3Og_g+2YEUCnPCB+YOdBEKkcUYqXN1Q@mail.gmail.com>
2012-01-05 18:15 ` Shriram Rajagopalan
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=20111219.163517.142436937064950002.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brendan@cs.ubc.ca \
--cc=hadi@cyberus.ca \
--cc=netdev@vger.kernel.org \
--cc=rshriram@cs.ubc.ca \
/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).