From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: brouer@redhat.com, cwang@twopensource.com,
netdev@vger.kernel.org, jpirko@redhat.com, mpatel@redhat.com
Subject: Re: [net-next PATCH] veth: don't assign a qdisc to veth
Date: Fri, 03 Oct 2014 14:56:04 -0700 (PDT) [thread overview]
Message-ID: <20141003.145604.344775445146119193.davem@davemloft.net> (raw)
In-Reply-To: <1412369519.17245.2.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 03 Oct 2014 13:51:59 -0700
> On Fri, 2014-10-03 at 22:38 +0200, Jesper Dangaard Brouer wrote:
>> On Fri, 3 Oct 2014 09:53:16 -0700
>> Cong Wang <cwang@twopensource.com> wrote:
>>
>> > On Fri, Oct 3, 2014 at 3:48 AM, Jesper Dangaard Brouer
>> > <brouer@redhat.com> wrote:
>> > > The veth driver is a virtual device, and should not have assigned
>> > > the default qdisc. Verified (ndo_start_xmit) veth_xmit can only
>> > > return NETDEV_TX_OK, thus this should be safe to bypass qdisc.
>> > >
>> > > Not assigning a qdisc is subtly done by setting tx_queue_len to zero.
>> > >
>> >
>> > Huh?? Maybe your $subject is too misleading, but we do use HTB
>> > on veth, this will break our code since we will have to set tx_queue_len
>> > after your patch, no?
>>
>> No, you HTB setup should still work.
>
> Unfortunately no....
>
> Default htb classes are pfifo, and this uses device txqueuelen as
> default limit.
>
> So your change should have been done years ago.
>
> Now its too late as it can break existing user scripts.
Agreed, this change cannot be made.
prev parent reply other threads:[~2014-10-03 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 10:48 [net-next PATCH] veth: don't assign a qdisc to veth Jesper Dangaard Brouer
2014-10-03 16:53 ` Cong Wang
2014-10-03 20:38 ` Jesper Dangaard Brouer
2014-10-03 20:48 ` Cong Wang
2014-10-03 20:51 ` Eric Dumazet
2014-10-03 21:56 ` 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=20141003.145604.344775445146119193.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=cwang@twopensource.com \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=mpatel@redhat.com \
--cc=netdev@vger.kernel.org \
/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).