From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv4: make arp seq_file show method only produce one record per call
Date: Wed, 16 Oct 2002 22:11:08 -0300 [thread overview]
Message-ID: <20021017011108.GT7541@conectiva.com.br> (raw)
In-Reply-To: <20021016.175809.28811497.davem@redhat.com>
Em Wed, Oct 16, 2002 at 05:58:09PM -0700, David S. Miller escreveu:
> From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
> Date: Wed, 16 Oct 2002 22:01:36 -0300
>
> Please pull from:
>
> master.kernel.org:/home/acme/BK/net-2.5
>
> Pulled, thanks.
>
> Now to help Al create a sane mechanism for carrying private state
> around between start/stop :-)
That would be nice, yes, bastardizing pos for this is, humm, ugly, and
it isn't accessible at show time (pun intended 8) ).
But now I have to chainsaw the /proc/net/route support into shape, and
this one will be fun, as I'll have to change the semantics of the
struct fib_table tb_seq_show so that I can grab the lock at fib_seq_start,
and at fib_seq_show pass just one entry, then drop the lock at fib_seq_stop.
So, probably we'll have fib_table::tb_seq_{start, next, show, start}, humm,
this gave another idea... :)
- Arnaldo
next prev parent reply other threads:[~2002-10-17 1:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 1:01 [PATCH] ipv4: make arp seq_file show method only produce one record per call Arnaldo Carvalho de Melo
2002-10-17 0:58 ` David S. Miller
2002-10-17 1:11 ` Arnaldo Carvalho de Melo [this message]
2002-10-17 1:15 ` David S. Miller
2002-10-17 1:30 ` Neil Brown
2002-10-17 1:28 ` David S. Miller
2002-10-17 2:00 ` Arnaldo Carvalho de Melo
2002-10-17 2:10 ` Arnaldo Carvalho de Melo
2002-10-17 2:23 ` Arnaldo Carvalho de Melo
2002-10-17 1:35 ` Arnaldo Carvalho de Melo
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=20021017011108.GT7541@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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