From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: netdev@vger.kernel.org, olaf.kirch@oracle.com
Subject: Re: [PATCH][RFC] network splice receive v2
Date: Wed, 13 Jun 2007 12:01:04 +0400 [thread overview]
Message-ID: <20070613080103.GA24701@2ka.mipt.ru> (raw)
In-Reply-To: <20070612181731.GQ18832@kernel.dk>
On Tue, Jun 12, 2007 at 08:17:32PM +0200, Jens Axboe (jens.axboe@oracle.com) wrote:
> On Tue, Jun 12 2007, Evgeniy Polyakov wrote:
> > On Mon, Jun 11, 2007 at 01:59:26PM +0200, Jens Axboe (jens.axboe@oracle.com) wrote:
> > > Patches are against the #splice branch of the block repo, "official" url
> > > of that is:
> > >
> > > git://git.kernel.dk/data/git/linux-2.6-block.git/
> > >
> > > and it's based on Linus main tree. Let me know if I should supply netdev
> > > branch patches instead, or even just provide a rolled up patch (or patch
> > > series) for anyone curious to test or play with it.
> >
> > Hi Jens.
> >
> > I've just pulled your tree (splice-net, but splice tree looks the
> > same, git pull says 'Already up-to-date.') on top of linus git and got
> > following bug trace. I will investigate it further tomorrow.
>
> Please tell me the contents of splice-net, it looks like you didn't
> actually use the new code. That BUG_ON() is in get_page(), which
> splice-net no longer uses. So the bug report cannot be valid for the
> current code.
This is the last commit in that tree:
commit c90a6ce8242d108a5bc6fd0bc1b2aca72a2b5944
Author: Jens Axboe <jens.axboe@oracle.com>
Date: Mon Jun 11 21:59:50 2007 +0200
TCP splice receive support
Support for network splice receive.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
:100644 100644 efc4517... 472ee12... M include/linux/net.h
:100644 100644 e7367c7... 64e3eed... M include/linux/skbuff.h
:100644 100644 a8af9ae... 8e86697... M include/net/tcp.h
:100644 100644 7c6a34e... daea7b0... M net/core/skbuff.c
:100644 100644 041fba3... 0ff9f86... M net/ipv4/af_inet.c
:100644 100644 450f44b... 63efd7a... M net/ipv4/tcp.c
:100644 100644 f453019... 41240f5... M net/socket.c
I will rebase my tree, likely something was not merged correctly.
> --
> Jens Axboe
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-06-13 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 11:59 [PATCH][RFC] network splice receive v2 Jens Axboe
2007-06-12 18:17 ` Evgeniy Polyakov
2007-06-12 18:17 ` Jens Axboe
2007-06-12 18:18 ` Jens Axboe
2007-06-13 8:01 ` Evgeniy Polyakov [this message]
2007-06-13 19:50 ` Jens Axboe
2007-06-14 11:57 ` Evgeniy Polyakov
2007-06-14 11:59 ` Jens Axboe
2007-06-15 8:06 ` Evgeniy Polyakov
2007-06-15 8:43 ` Jens Axboe
2007-06-15 9:14 ` Evgeniy Polyakov
2007-06-15 9:34 ` Jens Axboe
2007-06-15 9:44 ` Evgeniy Polyakov
2007-06-15 13:31 ` Jens Axboe
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=20070613080103.GA24701@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=jens.axboe@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=olaf.kirch@oracle.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;
as well as URLs for NNTP newsgroup(s).