All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	"David S. Miller" <davem@davemloft.net>
Subject: [PATCH 0/4] avoid disabling interrupts where it is not required
Date: Fri,  4 May 2018 16:24:42 +0200	[thread overview]
Message-ID: <20180504142446.30525-1-bigeasy@linutronix.de> (raw)

This series avoids/limits disabling of interrupts in drivers/ide.
This is from the -RT queue where it was reported initially (ata was not
widespread back then) and it hurts -RT.

While looking at alim15x3, there are some drivers which exist in both
worlds (alim15x3 included was far as I can tell). Is there a reason why
we still keep two drivers around for the same hardware? I know on mips
bigsur and swarm select IDE in their defconfig. I fixed (ages ago) ide
for swarm while I was using ata myself. So *I* think this just a relict.
If Ralf's bigsur is still alive, it is using SATA and not the onboard
IDE.

Sebastian

             reply	other threads:[~2018-05-04 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 14:24 Sebastian Andrzej Siewior [this message]
2018-05-04 14:24 ` [PATCH 1/4] alim15x3: move irq-restore before pci_dev_put() Sebastian Andrzej Siewior
2018-05-04 17:37   ` David Miller
2018-05-04 14:24 ` [PATCH 2/4] ide: Handle irq disabling consistently Sebastian Andrzej Siewior
2018-05-04 17:38   ` David Miller
2018-05-04 14:24 ` [PATCH 3/4] ide: don't disable interrupts during kmap_atomic() Sebastian Andrzej Siewior
2018-05-04 17:38   ` David Miller
2018-05-04 14:24 ` [PATCH 4/4] ide: don't enable/disable interrupts in force threaded-IRQ mode Sebastian Andrzej Siewior
2018-05-04 17:39   ` David Miller

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=20180504142446.30525-1-bigeasy@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.