From: Stephen Hemminger <stephen@networkplumber.org>
To: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>,
Ed Swierk <eswierk@skyportsystems.com>,
netdev@vger.kernel.org, Benjamin Warren <ben@skyportsystems.com>,
Keith Holleman <holleman@skyportsystems.com>
Subject: Re: [PATCH] veth: Optionally pad packets to minimum Ethernet length
Date: Tue, 12 Dec 2017 10:34:23 -0800 [thread overview]
Message-ID: <20171212103423.508ad7c9@xeon-e3> (raw)
In-Reply-To: <20171212181817.GB3531@localhost.localdomain>
On Tue, 12 Dec 2017 16:18:17 -0200
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> wrote:
> On Tue, Dec 12, 2017 at 11:32:46AM -0600, Dan Williams wrote:
> > On Tue, 2017-12-12 at 08:13 -0800, Ed Swierk wrote:
> > > Most physical Ethernet devices pad short packets to the minimum
> > > length
> > > of 64 bytes (including FCS) on transmit. It can be useful to simulate
> > > this behavior when debugging a problem that results from it (such as
> > > incorrect L4 checksum calculation).
> > >
> > > Padding is unnecessary for most applications so leave it off by
> > > default. Enable padding only when the otherwise unused IFF_AUTOMEDIA
> > > flag is set (e.g. by writing 0x5003 to flags in sysfs).
> >
> > This seems like a weird overload of AUTOMEDIA, which no other driver
> > uses for this purpose. Seems like the only other user of AUTOMEDIA is
> > 8390/etherh.c for some 10BaseT/10Base2 stuff.
> >
> > I'm not sure what the interface should be, but perhaps a sysfs
> > attribute would be better than overloading IFF_AUTOMEDIA?
>
> What about using some tc action (i.e. skbmod) for this?
>
> Marcelo
Why not add to netdevsim rather than cluttering up a normal driver
with test support. We just pulled a bunch of test stuff out of dummy
for the same reason.
next prev parent reply other threads:[~2017-12-12 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 16:13 [PATCH] veth: Optionally pad packets to minimum Ethernet length Ed Swierk
2017-12-12 17:32 ` Dan Williams
2017-12-12 18:18 ` Marcelo Ricardo Leitner
2017-12-12 18:34 ` Stephen Hemminger [this message]
2017-12-12 19:00 ` Ed Swierk
2017-12-12 22:01 ` Stephen Hemminger
2017-12-12 21:11 ` Cong Wang
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=20171212103423.508ad7c9@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ben@skyportsystems.com \
--cc=dcbw@redhat.com \
--cc=eswierk@skyportsystems.com \
--cc=holleman@skyportsystems.com \
--cc=marcelo.leitner@gmail.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).