Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai-l3A5Bk7waGM@public.gmane.org>
To: Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org>
Cc: Torsten Schenk <torsten.schenk-ytc+IHgoah0@public.gmane.org>,
	alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] 6fire: fix URB transfer buffer for midi output
Date: Thu, 08 Aug 2013 08:03:39 +0200	[thread overview]
Message-ID: <s5hy58cafd0.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1308071334590.886-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>

At Wed, 7 Aug 2013 13:38:20 -0400 (EDT),
Alan Stern wrote:
> 
> On Wed, 7 Aug 2013, Takashi Iwai wrote:
> 
> > [Cc'ed to linux-usb ML]
> > 
> > At Wed, 7 Aug 2013 16:51:49 +0200,
> > Torsten Schenk wrote:
> > > 
> > > Patch fixes URB transfer buffer allocation for midi output to be DMA-able.
> > 
> > Is this really needed?
> > That is, can't a transfer buffer be at middle of kmalloc'ed space, but
> > must be always the head of the kmalloc'ed space?
> 
> A buffer _can_ be in the middle of a kmalloc'ed space, but the CPU must
> not access any of the fields around it that might occupy the same cache
> line while the buffer is being used for DMA.  In general, it's safest
> not to put any other data in the same kmalloc'ed region with a DMA
> buffer.

Hrm, but does the kmalloc buffer always guarantee such cache line
exclusiveness...?  I thought a simple one like SLOB doesn't care.


> > > @@ -32,7 +28,7 @@
> > >  	struct snd_rawmidi_substream *out;
> > >  	struct urb out_urb;
> > >  	u8 out_serial; /* serial number of out packet */
> > > -	u8 out_buffer[MIDI_BUFSIZE];
> > > +	u8 *out_buffer;
> > >  	int buffer_offset;
> 
> In this case, the CPU would access out_urb while out_buffer was in use.

OK, then we need to fix sound/usb/6fire/pcm.c, too.
Torsten, care to respin the patch?


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-08-08  6:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 14:51 [PATCH] 6fire: fix URB transfer buffer for midi output Torsten Schenk
     [not found] ` <20130807165149.188c4b16297be52c0630a18f-ytc+IHgoah0@public.gmane.org>
2013-08-07 16:34   ` Takashi Iwai
     [not found]     ` <s5hli4d5uj7.wl%tiwai-l3A5Bk7waGM@public.gmane.org>
2013-08-07 17:38       ` Alan Stern
     [not found]         ` <Pine.LNX.4.44L0.1308071334590.886-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-08-08  6:03           ` Takashi Iwai [this message]
2013-08-08  7:16             ` Clemens Ladisch
     [not found]               ` <520345CB.3030307-P6GI/4k7KOmELgA04lAiVw@public.gmane.org>
2013-08-08  7:28                 ` [alsa-devel] " Takashi Iwai
2013-08-11  9:11             ` [PATCH 1/2] 6fire: make buffers DMA-able (pcm) Torsten Schenk
2013-08-12  9:37               ` Takashi Iwai

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=s5hy58cafd0.wl%tiwai@suse.de \
    --to=tiwai-l3a5bk7wagm@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz@public.gmane.org \
    --cc=torsten.schenk-ytc+IHgoah0@public.gmane.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