From: David Miller <davem@davemloft.net>
To: ole@ans.pl
Cc: netdev@vger.kernel.org, jens.axboe@oracle.com, nickpiggin@yahoo.com.au
Subject: Re: [PATCH 2/2]: net: Do software flow seperation on receive.
Date: Fri, 26 Jun 2009 16:52:30 -0700 (PDT) [thread overview]
Message-ID: <20090626.165230.68583655.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0906270136390.23295@bizon.gios.gov.pl>
From: Krzysztof Oledzki <ole@ans.pl>
Date: Sat, 27 Jun 2009 01:40:35 +0200 (CEST)
> What is the future of this patch? Was it only a proof of concept or is
> it going to be included in the mainline one day?
Lots of work and thinking is necessary to do this right.
Maybe something will be integrated into my tree in the
next few months or so.
prev parent reply other threads:[~2009-06-26 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 2:34 [PATCH 2/2]: net: Do software flow seperation on receive David Miller
2009-06-26 23:40 ` Krzysztof Oledzki
2009-06-26 23:52 ` David Miller [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=20090626.165230.68583655.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jens.axboe@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=ole@ans.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).