All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: akmp@osdl.org
Cc: rdreier@cisco.com, davem@davemloft.net,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: [PATCH 0 of 2] Add memcpy_cachebypass, a memcpy that doesn't cache reads
Date: Wed, 29 Nov 2006 15:35:07 -0700	[thread overview]
Message-ID: <patchbomb.1164843307@eng-12.pathscale.com> (raw)

These patches add a memcpy that doesn't cache reads, and use it in the
ipath driver's OpenIB receive path.

This version incorporates a few changes asked for last time around by DaveM.

	<b

             reply	other threads:[~2006-11-29 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 22:35 Bryan O'Sullivan [this message]
2006-11-29 22:35 ` [PATCH 1 of 2] Add memcpy_cachebypass, a memcpy that tries to reduce cache pressure Bryan O'Sullivan
2006-11-29 22:35 ` [PATCH 2 of 2] IB/ipath - use memcpy_cachebypass in RDMA interrupt handler to reduce packet loss Bryan O'Sullivan
2006-12-01  5:38 ` [PATCH 0 of 2] Add memcpy_cachebypass, a memcpy that doesn't cache reads Andrew Morton
2006-12-01 17:13   ` Bryan O'Sullivan

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=patchbomb.1164843307@eng-12.pathscale.com \
    --to=bos@pathscale.com \
    --cc=akmp@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=rdreier@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.