From: "Séguier Régis" <rseguier@e-teleport.net>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
alan@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: via-velocity.c fix sleep-with-spinlock bug during MTU change
Date: Fri, 20 Jun 2008 18:50:55 +0200 [thread overview]
Message-ID: <485BDFEF.2090307@e-teleport.net> (raw)
In-Reply-To: <20080620103910.GA21227@electric-eye.fr.zoreil.com>
Francois Romieu a écrit :
> Séguier Régis <rseguier@e-teleport.net> :
> [...]
>
>> But if I generate a paquet with a size more than around 3825, the driver
>> don't send it and no paquet is send after, work again after an interface
>> down/up and until no paquet > 3825.
>>
>
> Does it qualify as a regression ?
>
>
I couldn't say yes now.
To be honest, I never test mtu > 1500 with this driver before.
This can be detected before with the difficulty of mtu change?
I'll test the driver before patch with a bigger MTU. (i'll try to do
this next week)
--
Régis
next prev parent reply other threads:[~2008-06-20 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 1:46 [PATCH] net: via-velocity.c fix sleep-with-spinlock bug during MTU change Arjan van de Ven
2008-06-03 20:40 ` Andrew Morton
2008-06-03 21:51 ` Francois Romieu
2008-06-04 21:59 ` Francois Romieu
2008-06-14 21:23 ` Francois Romieu
2008-06-16 17:21 ` Séguier Régis
2008-06-16 21:17 ` Séguier Régis
2008-06-16 21:25 ` Séguier Régis
2008-06-17 21:45 ` Francois Romieu
2008-06-17 23:37 ` Séguier Régis
2008-06-18 16:56 ` Séguier Régis
2008-06-18 20:10 ` Francois Romieu
2008-06-18 22:09 ` Séguier Régis
2008-06-19 20:43 ` Francois Romieu
2008-06-20 10:24 ` Séguier Régis
2008-06-20 10:39 ` Francois Romieu
2008-06-20 16:50 ` Séguier Régis [this message]
2008-06-23 17:04 ` Séguier Régis
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=485BDFEF.2090307@e-teleport.net \
--to=rseguier@e-teleport.net \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.