From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, akepner@sgi.com
Subject: Re: [PATCH] Extend lock less TX to real devices
Date: Wed, 1 Sep 2004 22:33:01 -0700 [thread overview]
Message-ID: <20040901223301.1a8d97a8.davem@redhat.com> (raw)
In-Reply-To: <m38ybvjxdv.fsf@averell.firstfloor.org>
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.
> I added support for trylocking instead of spinning like sch_generic
> does - for that the driver has to return -1, then the packet is requeued.
> The check for a local device deadlock is lost for this case,
> but that doesn't seem to be a big loss (I've never seen this printk
> ever get triggered)
It is triggerable if you misconfigure your system.
I'm totally against this change, because previously at
least the user would find out in their logs. With your
change the system explodes looping with no explanation why.
> The patch looks bigger than it really is because i moved some code
> around and converted the macros into inlines.
..
> I also did an additional micro optimization:
And for this reason you need to split this patch up.
I would recommend:
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
Thanks Andi.
next prev parent reply other threads:[~2004-09-02 5:33 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 [this message]
2004-09-04 13:28 ` Andi Kleen
2004-09-04 14:11 ` jamal
2004-09-04 14:24 ` Andi Kleen
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=20040901223301.1a8d97a8.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@muc.de \
--cc=akepner@sgi.com \
--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).