From: Daniel Borkmann <dborkman@redhat.com>
To: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Cc: jbrouer@redhat.com, netdev@vger.kernel.org
Subject: Re: TX_RING and VLAN : (packet size is too long 1518 > 1514)
Date: Mon, 24 Feb 2014 23:33:36 +0100 [thread overview]
Message-ID: <530BC8C0.6040004@redhat.com> (raw)
In-Reply-To: <530B0AC9.9080003@fokus.fraunhofer.de>
On 02/24/2014 10:03 AM, Mathias Kretschmer wrote:
...
> I've manually merged your patch into 3.10.32 since this is what I'm using right now.
>
> Yes, it works here. We can now send full-sized VLAN-tagged frames via TX_RING.
Ok, thanks, I will submit it some time this week, after some more
testing from my side as well.
next prev parent reply other threads:[~2014-02-24 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 11:03 TX_RING and VLAN : (packet size is too long 1518 > 1514) Mathias Kretschmer
2014-02-23 13:58 ` Daniel Borkmann
2014-02-24 9:03 ` Mathias Kretschmer
2014-02-24 22:33 ` Daniel Borkmann [this message]
2014-02-26 7:28 ` Mathias Kretschmer
2014-02-26 10:33 ` Daniel Borkmann
2014-02-24 21:40 ` Setting skb->protocol efficiently for AF_PACKETs via TX_RING Mathias Kretschmer
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=530BC8C0.6040004@redhat.com \
--to=dborkman@redhat.com \
--cc=jbrouer@redhat.com \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--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).