[Top] [All Lists]

Re: LLTX and netif_stop_queue

To: hadi@xxxxxxxxxx
Subject: Re: LLTX and netif_stop_queue
From: Eric Lemoine <eric.lemoine@xxxxxxxxx>
Date: Wed, 22 Dec 2004 19:49:48 +0100
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, Roland Dreier <roland@xxxxxxxxxxx>, netdev@xxxxxxxxxxx, openib-general@xxxxxxxxxx
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=e9BhxdMCrPpdlobEkEt0glU1RdXhnXYNfTK3fC34M1bshKe6dazKYfahzW16/1TqR/7S3wgYnKmfFAfUS13GRHnNN9iwZ9LSQORe3aN7emgBB3ENRJwjm6LfwBRNom5uj1NXO661yT3uaJ9wton6ScXELgPSIivSa/CT+zigDt4=
In-reply-to: <1103484675.1050.158.camel@xxxxxxxxxxxxxxxx>
References: <52llbwoaej.fsf@xxxxxxxxxxx> <20041217214432.07b7b21e.davem@xxxxxxxxxxxxx> <1103484675.1050.158.camel@xxxxxxxxxxxxxxxx>
Reply-to: Eric Lemoine <eric.lemoine@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On 19 Dec 2004 14:31:15 -0500, jamal <hadi@xxxxxxxxxx> wrote:
> On Sat, 2004-12-18 at 00:44, David S. Miller wrote:
> > Perhaps one way to fix this is to add a pointer to a spinlock to
> > the netdev struct, and have hold that the upper level grab that
> > when NETIF_F_LLTX when doing queue state checks.  Actually, that
> > could end up being racy too.
> How about releasing the qlock only when the LLTX transmit lock is
> grabbed? That should bring it to par with what it was originally.

I dont like the idea of releasing inside the driver a lock taken
outside. That might be just me...

Instead, I would suggest to have LLTX drivers check whether queue is
stopped after they grab their private tx lock and before they check tx
ring fullness. That way we close the race window but keep the driver
bug check around.

See attached sungem patch.


Attachment: sungem-lltx.patch
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>