| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: af_packet & CHECKSUM_HW |
| From: | Petr Vandrovec <vandrove@xxxxxxxxxx> |
| Date: | Mon, 17 Nov 2003 20:44:52 +0100 |
| Cc: | James Morris <jmorris@xxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <20031116205146.GA8477@gondor.apana.org.au> |
| References: | <20031115024434.GA12276@gondor.apana.org.au> <Xine.LNX.4.44.0311160841500.31201-100000@thoron.boston.redhat.com> <20031116205146.GA8477@gondor.apana.org.au> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.4i |
On Mon, Nov 17, 2003 at 07:51:46AM +1100, Herbert Xu wrote:
> On Sun, Nov 16, 2003 at 08:44:38AM -0500, James Morris wrote:
> > On Sat, 15 Nov 2003, Herbert Xu wrote:
> >
> > > In other words, what do I tell confused users who see bad checksums
> > > in the tcpdump output over loopback and interfaces capable of
> > > hardware checksums?
> >
> > That this functionality does not belong in the kernel, as it serves no
> > real purpose.
>
> OK, I will quote you on that :)
It would be nice if at least kernel did not stomp on skb2->h.raw so
ptype callback could cope with situation and report to userspace where
to put checksum. I already discussed it here two or so months ago, and
only solution I was able to find is that VMware's vmnet have to parse
itself network headers to find where to put checksum. Nothing for IPv6
users...
Best regards,
Petr Vandrovec
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH]: Adjust qlen when grafting in multiple qdiscs, Werner Almesberger |
|---|---|
| Next by Date: | Re: af_packet & CHECKSUM_HW, David S. Miller |
| Previous by Thread: | Re: af_packet & CHECKSUM_HW, Herbert Xu |
| Next by Thread: | Re: af_packet & CHECKSUM_HW, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |