From: Andi Kleen <ak@suse.de>
To: jamal <hadi@cyberus.ca>
Cc: Andi Kleen <ak@muc.de>, "David S. Miller" <davem@redhat.com>,
Alexey <kuznet@ms2.inr.ac.ru>,
netdev@oss.sgi.com, akepner@sgi.com
Subject: Re: [PATCH] Extend lock less TX to real devices
Date: Sat, 4 Sep 2004 16:24:04 +0200 [thread overview]
Message-ID: <20040904142404.GA6850@wotan.suse.de> (raw)
In-Reply-To: <1094307106.1634.147.camel@jzny.localdomain>
On Sat, Sep 04, 2004 at 10:11:46AM -0400, jamal wrote:
> On Sat, 2004-09-04 at 09:28, Andi Kleen wrote:
> > On Wed, Sep 01, 2004 at 10:33:01PM -0700, David S. Miller wrote:
> > > On Tue, 31 Aug 2004 14:38:20 +0200
> > > Andi Kleen <ak@muc.de> wrote:
> > >
> > > > This patch extends the recently added NETIF_F_LLTX to real devices.
> > >
> > > Well, it does a lot of other things too.
> >
> > Not really, it all works to the same goal.
>
> Must be my sleep depravation - what is LLTX again?
NETIF_F_LLTX - a new flag that tells the stack the the driver
doesn't want an xmit lock.
>
>
> > > least the user would find out in their logs. With your
> > > change the system explodes looping with no explanation why.
> >
> > Hmm, I guess if you're really worried about this class
> > of driver bugs ble eing common adding some real error handling
> > for it (like bailing out and disabling the device) would
> > be the far better option.
>
> Actually that message is pretty useful.
> I have seen at least a handful of badly written drivers do that.
They will still print that, no problem.
>
> > > patch 1) Change macros into inlines
> > > patch 2) local_bh_disable() preemption count optimization
> > > patch 3) support for F_LLTX on real devices
> > > patch 4) locking changes
> >
> > At least (3) and (4) are the same thing. I can drop the
> > inlines, it was only for making the code clearer and less ugly
> > but is not essential for the optimizations.
>
> do you guys mind if i test these patches/patch out first before final
> inclusion? Next weekend i will have the chance.
You can do that, but they won't do much unless your driver sets
NETIF_F_LLTX.
-Andi
next prev parent reply other threads:[~2004-09-04 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 12:38 [PATCH] Extend lock less TX to real devices Andi Kleen
2004-09-02 5:33 ` David S. Miller
2004-09-04 13:28 ` Andi Kleen
2004-09-04 14:11 ` jamal
2004-09-04 14:24 ` Andi Kleen [this message]
2004-09-04 19:39 ` Herbert Xu
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=20040904142404.GA6850@wotan.suse.de \
--to=ak@suse.de \
--cc=ak@muc.de \
--cc=akepner@sgi.com \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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 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).