public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: David Miller <davem@davemloft.net>
Cc: xiaosuo@gmail.com, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
	jmorris@namei.org, kaber@trash.net, netdev@vger.kernel.org,
	YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH] fragment: add fast path
Date: Mon, 14 Jun 2010 14:15:17 +0900	[thread overview]
Message-ID: <4C15BAE5.6010900@linux-ipv6.org> (raw)
In-Reply-To: <20100613.181857.189703148.davem@davemloft.net>

David Miller wrote:
>> As the fragments are usually in order,
> 
> In what universe does this happen "usually"?
> 
> Linux has been outputting fragments in reverse order for more than 10
> years.
> 
> I'm not applying this patch.

Dave,  I know we've been sending in reverse order, of course.
And, as far as I know, it seems Linux is the only implementation
which sends fragments in reverse order.

This is receiving side.  I think we should accept the fact
that Linux is not the only implementation, no?

--yoshfuji

  parent reply	other threads:[~2010-06-14  5:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 23:16 [PATCH] fragment: add fast path Changli Gao
2010-06-14  1:18 ` David Miller
2010-06-14  2:03   ` Changli Gao
2010-06-14  2:24     ` YOSHIFUJI Hideaki
2010-06-14  2:52       ` Changli Gao
2010-06-14  2:55     ` Changli Gao
2010-06-14  5:15   ` YOSHIFUJI Hideaki [this message]
2010-06-14  6:19     ` Mitchell Erblich
2010-06-14  5:35 ` Eric Dumazet
2010-06-14  5:59   ` Changli Gao
2010-06-14  7:04     ` Eric Dumazet
2010-06-14 10:15       ` Changli Gao
2010-06-14  6:40   ` Eric Dumazet

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=4C15BAE5.6010900@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@vger.kernel.org \
    --cc=pekkas@netcore.fi \
    --cc=xiaosuo@gmail.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