From: kuznet@ms2.inr.ac.ru
To: adilger@turbolabs.com (Andreas Dilger)
Cc: davem@redhat.com, tim@physik3.uni-rostock.de,
jgarzik@mandrakesoft.com, andrewm@uow.edu.au,
linux-kernel@vger.kernel.org, torvalds@transmeta.com,
netdev@oss.sgi.com, ak@muc.de
Subject: Re: [PATCH] net/ipv4/*, net/core/neighbour.c jiffies cleanup
Date: Thu, 8 Nov 2001 21:32:32 +0300 (MSK) [thread overview]
Message-ID: <200111081832.VAA24875@ms2.inr.ac.ru> (raw)
In-Reply-To: <20011108111024.X5922@lynx.no> from "Andreas Dilger" at Nov 8, 1 11:10:24 am
Hello!
> is more likely that nobody knows about them, because nobody uses them,
> because nobody knows about them, etc.
Yes, it is thing which usually happens with good macros. :-)
> If people don't want to see them, that is fine with me - they will stop.
I talk only about neighbour.c. It is pretty hairy to bring it to
brain cache fastly enough. And I am afraid (remember) that in the past
I did some silly tricks, sort of using the fact that large positive
now - mark means that mark is in future. Mostly likely killed together
with another hacks, but I am not sure.
Another places are trivial as rule and can be edited any time.
Alexey
next prev parent reply other threads:[~2001-11-08 18:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 0:00 Tim Schmielau
2001-11-08 0:09 ` David S. Miller
2001-11-08 0:36 ` Andreas Dilger
2001-11-08 1:22 ` Linus Torvalds
2001-11-08 0:44 ` David S. Miller
2001-11-08 0:58 ` Tim Schmielau
2001-11-08 1:09 ` David S. Miller
2001-11-08 1:20 ` Tim Schmielau
2001-11-08 1:36 ` David S. Miller
2001-11-08 4:32 ` Andreas Dilger
2001-11-08 4:39 ` David S. Miller
2001-11-08 17:54 ` kuznet
2001-11-08 18:10 ` Tim Schmielau
2001-11-08 18:10 ` Andreas Dilger
2001-11-08 18:32 ` kuznet [this message]
2001-11-08 3:07 Krishna Kumar
2001-11-08 5:26 ` Linus Torvalds
2001-11-08 16:55 Krishna Kumar
2001-11-08 17:10 ` Linus Torvalds
2001-11-08 18:01 ` Andreas Dilger
2001-11-09 10:43 ` Vino Thomas
2001-11-08 17:47 Krishna Kumar
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=200111081832.VAA24875@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=adilger@turbolabs.com \
--cc=ak@muc.de \
--cc=andrewm@uow.edu.au \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tim@physik3.uni-rostock.de \
--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®