netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: michaelc@cs.wisc.edu
Cc: jesse.brandeburg@intel.com, netdev@vger.kernel.org,
	olaf.kirch@oracle.com, tgraf@suug.ch, kkeil@suse.de,
	herbert@gondor.apana.org.au
Subject: Re: [PANIC] lro + iscsi or lro + skb text search causes panic
Date: Sun, 25 Jan 2009 21:34:36 -0800 (PST)	[thread overview]
Message-ID: <20090125.213436.268287293.davem@davemloft.net> (raw)
In-Reply-To: <49794612.9010204@cs.wisc.edu>

From: Mike Christie <michaelc@cs.wisc.edu>
Date: Thu, 22 Jan 2009 22:22:42 -0600

> Attached is a patch made against the scsi maintainer's tree (I think
> it should also apply to linus's) that converts iscsi to use
> skb_copy_bits. It is lightly tested. If there is no benefit in
> having skb_find_text use skb_seq_read maybe we can just kill it, so
> people do not have to maintain two helpers that provide similar
> functionality.

Regardless of what we decide to do with iSCSI we have to make this
function work properly as long as there is a user in the tree.

This iterator can in fact be more efficient than using copy
bits since copy bits doesn't remember any state from previous
invocations whereas the iterator does.  So if you call it
multiple times on the same SKB that's a lot of wasted work.

In fact I'm pretty sure that's why we added it for textsearch,
because in that application we're constantly beating through
the same SKB via the testsearch state machine.

Therefore, keeping it's use for iSCSI would be beneficial.

  parent reply	other threads:[~2009-01-26  5:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 20:55 [PANIC] lro + iscsi or lro + skb text search causes panic Brandeburg, Jesse
2009-01-22 22:49 ` Mike Christie
2009-01-23  4:22   ` Mike Christie
2009-01-23  4:29     ` Mike Christie
2009-01-26  5:34     ` David Miller [this message]
2009-01-22 23:21 ` Herbert Xu
2009-01-22 23:45   ` Brandeburg, Jesse
2009-01-23  0:04   ` Mike Christie
2009-01-26  5:32     ` David Miller
2009-01-26 22:30       ` Herbert Xu
2009-01-27  1:40         ` Brandeburg, Jesse
2009-01-27  3:01           ` Herbert Xu
2009-01-27  5:52         ` David Miller
2009-01-27  6:12         ` Mike Christie
     [not found]           ` <46A00B48CC54E4468EF6911F877AC4CA01EF2BC9@blrx3m10.blr.amer.dell.com>
2009-01-28 21:25             ` Herbert Xu
2009-01-30  0:13               ` David Miller
2009-01-26 20:54     ` Mike Christie
  -- strict thread matches above, loose matches on Subject: below --
2009-01-28 12:36 Shyam_Iyer
2009-01-28 18:22 ` Mike Christie

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=20090125.213436.268287293.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jesse.brandeburg@intel.com \
    --cc=kkeil@suse.de \
    --cc=michaelc@cs.wisc.edu \
    --cc=netdev@vger.kernel.org \
    --cc=olaf.kirch@oracle.com \
    --cc=tgraf@suug.ch \
    /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).