netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: [IPV4] Check mtu instead of frag_list in ip_push_pending_frames
Date: Wed, 23 Mar 2005 12:20:02 -0800	[thread overview]
Message-ID: <20050323122002.04fc046e.davem@davemloft.net> (raw)
In-Reply-To: <20050321105622.GA23809@gondor.apana.org.au>

On Mon, 21 Mar 2005 21:56:22 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:

> The fix is similar to what we did in ip_output.  Instead of checking
> whether frag_list is empty, we check the condition skb->len <= dst_mtu
> directly and set the DF bit based on that.

Looks good, applied.

Thanks Herbert.

      parent reply	other threads:[~2005-03-23 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 10:56 [IPV4] Check mtu instead of frag_list in ip_push_pending_frames Herbert Xu
2005-03-21 11:16 ` [IPV4] Clear DF bit in ip_fragment fast path Herbert Xu
2005-03-23 20:20   ` David S. Miller
2005-03-23 20:20 ` David S. 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=20050323122002.04fc046e.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.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).