From: Jan Ceuleers <jan.ceuleers@computer.org>
To: Sameer Rahmani <lxsameer@lxsameer.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Share network traffic between processes with respect to a priority value.
Date: Mon, 23 Jul 2012 20:55:00 +0200 [thread overview]
Message-ID: <500D9E04.8080306@computer.org> (raw)
In-Reply-To: <500D6E28.8020200@lxsameer.com>
On 07/23/2012 05:30 PM, Sameer Rahmani wrote:
> Hi guys.
> What do you think about the idea ?
What little old me thinks about the idea is that it is not fully formed (i.e. it could do with more detail), and that you have posted in the wrong place (i.e. the networking guys hang out on the netdev mailing list).
So can I suggest that you write two or three paragraphs describing your idea and why it is desirable, and then two or three paragraphs more about how the kernel's behaviour would need to change to implement it, and then post that to netdev@vger.kernel.org ?
KR, Jan
prev parent reply other threads:[~2012-07-23 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:30 Share network traffic between processes with respect to a priority value Sameer Rahmani
2012-07-23 18:55 ` Jan Ceuleers [this message]
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=500D9E04.8080306@computer.org \
--to=jan.ceuleers@computer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxsameer@lxsameer.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