mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: linux-kernel@vger.kernel.org, cluster-devel@redhat.com,
	Al Viro <viro@zeniv.linux.org.uk>,
	nstraz@redhat.com
Subject: Re: seq_file: Use larger buffer to reduce time traversing lists
Date: Fri, 01 Jun 2012 14:48:10 +0200	[thread overview]
Message-ID: <1338554890.2760.1517.camel@edumazet-glaptop> (raw)
In-Reply-To: <1338553486.2708.25.camel@menhir>

On Fri, 2012-06-01 at 13:24 +0100, Steven Whitehouse wrote:

> Yes, you are right that it will be slow, still. But I'm not sure what we
> can do about that. We have to find our place again on each read call, in
> any case I think.

You dont really answer my question, I asked the exact timing...

I can't reproduce this slow behavior you have, using /proc/net seq
files.

Isn't it a problem with this particular file ?

Does it want to output a single record ( m->op->show(m, p) ) much larger
than 4KB ?




  reply	other threads:[~2012-06-01 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01 10:39 Steven Whitehouse
2012-06-01 12:10 ` Eric Dumazet
2012-06-01 12:14   ` Eric Dumazet
2012-06-01 12:26     ` Steven Whitehouse
2012-06-01 12:24   ` Steven Whitehouse
2012-06-01 12:48     ` Eric Dumazet [this message]
2012-06-01 13:14       ` Steven Whitehouse
2012-06-01 13:27         ` Eric Dumazet
2012-06-01 14:18           ` Steven Whitehouse
2012-06-01 14:57             ` Eric Dumazet
2012-06-01 15:01               ` Eric Dumazet
2012-06-01 15:18                 ` Eric Dumazet
2012-06-01 15:30                   ` Steven Whitehouse
2012-06-01 15:28               ` Steven Whitehouse
2012-06-01 15:47                 ` Eric Dumazet
2012-06-01 15:54 ` Joe Perches

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=1338554890.2760.1517.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nstraz@redhat.com \
    --cc=swhiteho@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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®