mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: maxk@qualcomm.com (Maksim Krasnyanskiy)
Cc: davem@redhat.com, linux-kernel@vger.kernel.org, andrea@suse.de,
	torvalds@transmeta.com
Subject: Re: [PATCH] netif_rx from non interrupt context
Date: Tue, 31 Jul 2001 22:13:27 +0400 (MSK DST)	[thread overview]
Message-ID: <200107311813.WAA09018@ms2.inr.ac.ru> (raw)
In-Reply-To: <4.3.1.0.20010731100209.05fce100@mail1> from "Maksim Krasnyanskiy" at Jul 31, 1 10:11:49 am

Hello!

> a critical path. Also it makes sense (to me) to hide softirq implementation details from the net drivers.

He tells right thing... The fact that netif_rx() is invalid in this context
and, especially, way to make it valid is not evident. It was not evident
for me three days ago, at least. :-)

Seems, it is better to hide this yet.

Alexey

      reply	other threads:[~2001-07-31 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-30 19:24 Maksim Krasnyanskiy
2001-07-31  1:53 ` David S. Miller
2001-07-31 17:11 ` Maksim Krasnyanskiy
2001-07-31 18:13   ` kuznet [this message]

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=200107311813.WAA09018@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=andrea@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®